Security
Roblox-only, by construction.
Server-side authorization and protected-change approvals help keep development scoped to the Studio project you select.
Authorized Studio connections
Potato AI for Windows↓Potato Bridge↓Roblox Studio MCP
- Local Studio connections use authenticated loopback services. Remote API communication uses HTTPS.
- Potato AI manages its Studio plugin and available tool integrations. Connection does not grant approval for protected changes.
- Unknown tool names are rejected by the Bridge itself, even if the backend ever asked.
All 20 tools. Nothing else exists.
This is the complete set the model can invoke. Anything not listed here cannot happen.
| Tool | Risk | What it does |
|---|---|---|
| potato_studio_status | READ_ONLY | Bridge + Studio presence and selection |
| potato_list_studios | READ_ONLY | Open Studio windows to choose between |
| potato_inspect_game | READ_ONLY | Game-tree search before any change |
| potato_inspect_instance | READ_ONLY | Properties of one instance |
| potato_read_script | READ_ONLY | Read script sources |
| potato_search_scripts | READ_ONLY | Find/duplicate-check scripts |
| potato_get_console | READ_ONLY | Playtest output for repair loop |
| potato_search_roblox_docs | READ_ONLY | Official documentation lookup |
| potato_search_roblox_assets | READ_ONLY | Search only — inserting needs approval |
| potato_capture_viewport | READ_ONLY | Visual verification screenshots |
| potato_start_playtest | SAFE_WRITE | Start a sandboxed playtest |
| potato_stop_playtest | SAFE_WRITE | Stop the playtest |
| potato_run_playtest_scenario | SAFE_WRITE | Scripted gameplay checks |
| potato_create_instances | SAFE_WRITE | Create new objects only |
| potato_generate_model | SAFE_WRITE | Procedural models, preferred over store assets |
| potato_generate_mesh | SAFE_WRITE | Generated meshes and materials |
| potato_apply_script_edit | SAFE_WRITE* | Script edits — upgrades to SENSITIVE_WRITE for 50+ line overwrites of your code |
| potato_update_instances | SAFE_WRITE* | Property updates — upgrades by blast radius |
| potato_execute_luau | SENSITIVE_WRITE | Arbitrary Luau always gated |
| potato_request_asset_insert | EXTERNAL_ASSET | Creator Store inserts always need Accept |
Risk policy
READ_ONLYPure reads. Never gated, always logged.
SAFE_WRITENew objects, Potato-owned edits, playtests. Automatic.
SENSITIVE_WRITELarge overwrites of your scripts, arbitrary Luau. Confirmation required.
EXTERNAL_ASSETAnything from outside your place. Confirmation + inspection required.
DESTRUCTIVELarge deletes and wipes. Confirmation required, backups first.
The policy engine — not the model — decides what needs approval. *Starred tools escalate dynamically by context.
Never collected
- ✕ Personal files or folders
- ✕ Browser history, cookies, passwords
- ✕ Installed apps or system settings
- ✕ Hardware identifiers
Stored, and why
- ✓ Bridge device id, name, OS, version, last seen
- ✓ Your projects, chats, plans, and change history
- ✓ Build preferences you save in Memory
- ✓ Billing and usage records (audit)
Account security
Sessions are server-side (Better Auth + Postgres). Every project, run, plan, and admin check re-verifies the session — browser-supplied user ids are never trusted. Suspended accounts cannot start builds. Bridges can be revoked instantly and stop working immediately.
Potato AI processes prompts and relevant project code to provide the service. Potato AI is independent and is not affiliated with Roblox Corporation.