Scan for newly installed games and refresh the library
AI agents call hydra_scan_library 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 performs a scan operation that discovers and catalogs games, which is fundamentally a read operation that queries the file system for existing games and refreshes internal library metadata. It has no side effects on user data, game files, or system configuration—it only refreshes the state of the library view.
From the tool's definition Tool name 'scan_library' and description 'Scan for newly installed games and refresh the library' indicates a read/query operation that detects and updates metadata about existing game installations without modifying game data, configurations, or system state…
Attacks that exploit this kind of access
Scan for newly installed games and refresh the library. 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_scan_library: 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_scan_library 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_scan_library 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_scan_library. 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_scan_library 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 →