Remove a game from the library. Optionally delete game files from disk.
AI agents call hydra_remove_game to permanently remove resources in Hydra Bridge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion operations: (1) removing a game from the library (metadata deletion) and (2) optionally deleting game files from disk (data destruction). These actions cannot be undone. The optional file deletion component makes this Destructive rather than merely Write.
From the tool's definition Tool name 'hydra_remove_game' combined with description 'Remove a game from the library. Optionally delete game files from disk.' explicitly indicates irreversible deletion of library entries and potentially game files.
Attacks that exploit this kind of access
Remove a game from the library. Optionally delete game files from disk. It is categorised as a Destructive tool in the Hydra Bridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hydra Bridge MCP server in PolicyLayer and add a rule for hydra_remove_game: 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 Hydra Bridge. Nothing to install.
hydra_remove_game 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 hydra_remove_game 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 hydra_remove_game. 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.
hydra_remove_game is provided by the Hydra Bridge MCP server (kleirrampage45/hydra-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →