upload_rom
Upload a local, user-provided game dump into Emulation/roms/<system> via SFTP.
This record as markdown: /tools/mcp-control-plane/upload-rom.md
What upload_rom does on Mcp Control Plane
AI agents use upload_rom to create or update resources in Mcp Control Plane, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Control Plane environment.
Why upload_rom is rated Medium
The tool uploads files to a remote system, which is a Write operation (creates new data). Severity is medium because: (1) it's reversible (uploaded files can be deleted), (2) blast radius is limited to the emulation ROM directory, and (3) the primary risk is storage consumption or accidental ROM uploads rather than system compromise. It does not execute code, delete irreversibly, or move money.
From the tool's definition Tool description states 'Upload a local, user-provided game dump into Emulation/roms/<system> via SFTP' — this creates/adds files to a remote filesystem.
Attacks that exploit this kind of access
The rule that runs upload_rom safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_rom, this is the rule to start with:
upload_rom stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every upload_rom call is checked against it from then on.
Questions about upload_rom
Upload a local, user-provided game dump into Emulation/roms/<system> via SFTP. It is categorised as a Write tool in the Mcp Control Plane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for upload_rom: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Control Plane. Nothing to install.
upload_rom is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the upload_rom rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for upload_rom. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
upload_rom is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue