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

steam_rom_manager_remove

Remove Steam ROM Manager shortcuts for selected parsers or all configured parsers.

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

This record as markdown: /tools/mcp-control-plane/steam-rom-manager-remove.md

What steam_rom_manager_remove does on Mcp Control Plane

AI agents call steam_rom_manager_remove to permanently remove resources in Mcp Control Plane, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why steam_rom_manager_remove is rated Critical

This tool performs irreversible deletion of Steam ROM Manager shortcut configurations. Even though the underlying ROM files remain intact, the removal of configured shortcuts and their metadata constitutes a destructive action that cannot be undone without manual reconfiguration.

From the tool's definition Tool name includes 'remove' and description states it removes Steam ROM Manager shortcuts, which is an irreversible deletion operation. The shortcuts, once removed, cannot be automatically recovered without reconfiguration.

Questions about steam_rom_manager_remove

What does the steam_rom_manager_remove tool do? +

Remove Steam ROM Manager shortcuts for selected parsers or all configured parsers. It is categorised as a Destructive tool in the Mcp Control Plane MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on steam_rom_manager_remove? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for steam_rom_manager_remove: 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_remove? +

steam_rom_manager_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit steam_rom_manager_remove? +

Yes. Add a rate_limit block to the steam_rom_manager_remove 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_remove completely? +

Set action: deny in the PolicyLayer policy for steam_rom_manager_remove. 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_remove? +

steam_rom_manager_remove 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.