steam_rom_manager_add
Run Steam ROM Manager add. Steam should be closed while shortcuts are written.
This record as markdown: /tools/mcp-control-plane/steam-rom-manager-add.md
What steam_rom_manager_add does on Mcp Control Plane
AI agents invoke steam_rom_manager_add to trigger actions in Mcp Control Plane. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why steam_rom_manager_add is rated High
The tool executes an external program (Steam ROM Manager) that writes shortcut files. This is an Execute action (running an external operation) with a Write side-effect. Since Execute > Write in severity ranking, it is classified as Execute. Misuse could corrupt Steam library shortcuts but is not irreversible in a destructive sense.
From the tool's definition 'Run Steam ROM Manager add' and 'shortcuts are written' — triggers an external application (Steam ROM Manager) that modifies Steam shortcut data on disk
Attacks that exploit this kind of access
The rule that runs steam_rom_manager_add 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 steam_rom_manager_add, this is the rule to start with:
steam_rom_manager_add stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 steam_rom_manager_add call is checked against it from then on.
Questions about steam_rom_manager_add
Run Steam ROM Manager add. Steam should be closed while shortcuts are written. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for steam_rom_manager_add: 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.
steam_rom_manager_add is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the steam_rom_manager_add 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 steam_rom_manager_add. 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.
steam_rom_manager_add 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.
Across the catalogue