steam_rom_manager_cli
Run Steam ROM Manager CLI arguments such as list, enable, disable, add, remove, or nuke.
This record as markdown: /tools/mcp-control-plane/steam-rom-manager-cli.md
What steam_rom_manager_cli does on Mcp Control Plane
AI agents call steam_rom_manager_cli 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_cli is rated Critical
The tool can execute destructive CLI operations including 'remove' and especially 'nuke', which implies irreversible deletion or wiping of data (ROM configurations, Steam library entries, etc.). 'Nuke' is a strong indicator of a mass-destructive, irreversible operation. Following the most-severe-applicable rule, Destructive takes precedence over Execute and Write.
From the tool's definition Run Steam ROM Manager CLI arguments such as list, enable, disable, add, remove, or nuke.
Attacks that exploit this kind of access
The rule that runs steam_rom_manager_cli 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_cli, this is the rule to start with:
steam_rom_manager_cli is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every steam_rom_manager_cli call is checked against it from then on.
Questions about steam_rom_manager_cli
Run Steam ROM Manager CLI arguments such as list, enable, disable, add, remove, or nuke. 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.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for steam_rom_manager_cli: 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_cli is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the steam_rom_manager_cli 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_cli. 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_cli 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