New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

steam_rom_manager_add

Run Steam ROM Manager add. Steam should be closed while shortcuts are written.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about steam_rom_manager_add

What does the steam_rom_manager_add tool do? +

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.

How do I enforce a policy on steam_rom_manager_add? +

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.

What risk level is steam_rom_manager_add? +

steam_rom_manager_add is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit steam_rom_manager_add? +

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.

How do I block steam_rom_manager_add completely? +

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.

What MCP server provides steam_rom_manager_add? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Control Plane's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.