Add a game to the download queue without starting immediately
AI agents use hydra_add_to_queue to create or update resources in Hydra Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hydra Bridge environment.
This tool creates or modifies queue state without irreversible destruction or executing arbitrary code. Adding to a queue is a reversible write operation (the download can be cancelled via hydra_cancel_download). It has medium severity because it commits bandwidth and storage resources, but is not destructive and does not immediately execute downloads.
From the tool's definition Tool description states 'Add a game to the download queue' — this creates a new entry in a queue, modifying the state of the download management system.
Attacks that exploit this kind of access
Add a game to the download queue without starting immediately. It is categorised as a Write tool in the Hydra Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hydra Bridge MCP server in PolicyLayer and add a rule for hydra_add_to_queue: 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_add_to_queue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hydra_add_to_queue 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_add_to_queue. 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_add_to_queue 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 →