Get game statistics (player count, downloads, reviews)
AI agents call hydra_get_game_stats 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 and retrieves read-only statistical data about games. It performs no modifications, deletions, code execution, or financial operations. The data returned (player count, downloads, reviews) are aggregated metrics that cannot be altered by a query. This is a straightforward Read category tool with low severity due to minimal blast radius if misused.
From the tool's definition Tool name and description indicate retrieval of game statistics: 'Get game statistics (player count, downloads, reviews)'. These are informational metrics with no side effects.
Attacks that exploit this kind of access
Get game statistics (player count, downloads, reviews). 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_game_stats: 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_game_stats 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_game_stats 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_game_stats. 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_game_stats 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 →