Send a download to the appropriate client
AI agents invoke download to trigger actions in Yarr Media Stack. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool initiates a download by sending a request to an external client (likely a Sonarr/Prowlarr download client). It executes an external operation whose effects depend on the arguments passed (e.g., which media to download). This is not merely writing metadata — it triggers real-world activity on external systems, consuming bandwidth, disk space, and potentially acquiring copyrighted content.
From the tool's definition "Send a download to the appropriate client" — triggers an external download operation
Attacks that exploit this kind of access
Send a download to the appropriate client. It is categorised as a Execute tool in the Yarr Media Stack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Yarr Media Stack MCP server in PolicyLayer and add a rule for 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 Yarr Media Stack. Nothing to install.
download is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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 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.
download is provided by the Yarr Media Stack MCP server (mcpnexus-registry/yarr). 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 →