Check what installer action is available for a game (e.g. needs install, ready to play)
AI agents call hydra_get_installer_action to retrieve information from Hydra Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the installation status or available actions for a game (install, ready to play, etc.). It performs a read-only lookup of game state data with no side effects, creation, modification, or deletion of data. The verb 'get' and phrase 'check what' confirm information retrieval only.
From the tool's definition Tool name 'hydra_get_installer_action' with description 'Check what installer action is available for a game' — uses 'get' and 'check' verbs indicating retrieval/query of game state without modification.
Attacks that exploit this kind of access
Check what installer action is available for a game (e.g. needs install, ready to play). It is categorised as a Read tool in the Hydra Bridge MCP Server, which means it retrieves data without modifying state.
Register the Hydra Bridge MCP server in PolicyLayer and add a rule for hydra_get_installer_action: 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_get_installer_action is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hydra_get_installer_action 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_get_installer_action. 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_get_installer_action 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 →