Cancel an active or queued download
AI agents call hydra_cancel_download to permanently remove resources in Hydra Bridge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling an active or queued download stops and discards the current download state. While the user could re-initiate the download, the in-progress state and any partially downloaded data are irreversibly lost. This is more severe than a simple Write (modify) action and aligns with Destructive since the current operation cannot be undone.
From the tool's definition Cancel an active or queued download — cancellation of a download is irreversible in the sense that the download progress is lost and the operation cannot be undone without restarting the download.
Attacks that exploit this kind of access
Cancel an active or queued download. It is categorised as a Destructive tool in the Hydra Bridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hydra Bridge MCP server in PolicyLayer and add a rule for hydra_cancel_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_cancel_download is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hydra_cancel_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_cancel_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_cancel_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 →