Move a download to a different area (hero=active, queue=waiting, paused=stopped)
AI agents use hydra_reorder_download 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 reorganizes/reorders downloads between states (active, queued, paused). It modifies the state of a download entry but does not delete data or execute arbitrary code. The change is reversible — a download can be moved back. This is a Write operation with low severity since misuse only affects download queue ordering.
From the tool's definition Move a download to a different area (hero=active, queue=waiting, paused=stopped)
Attacks that exploit this kind of access
Move a download to a different area (hero=active, queue=waiting, paused=stopped). 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_reorder_download: 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_reorder_download 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_reorder_download 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_reorder_download. 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_reorder_download 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 →