Add a new download source by URL
AI agents use hydra_add_download_source 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 application configuration by adding a new download source, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. Severity is medium because a malicious download source could potentially facilitate trojan/malware distribution if the agent is compromised, but the impact is limited to the Hydra Launcher application's scope.
From the tool's definition Tool name contains 'add' and description states 'Add a new download source by URL', indicating creation of a new configuration entry.
Attacks that exploit this kind of access
Add a new download source by URL. 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_download_source: 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_download_source 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_download_source 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_download_source. 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_download_source 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 →