download_release · Sonarr MCP Server MCP: Risk & Policy

WHAT IT DOES

What download_release does on Sonarr MCP Server

AI agents invoke download_release to trigger actions in Sonarr MCP Server. 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.

WHY IT NEEDS A POLICY

Why download_release needs a policy

Downloading a release initiates an external operation (fetching and storing media content) that has side effects beyond simple data writes. It triggers Sonarr to fetch content from external sources, consume bandwidth and storage, and potentially interact with download clients. This is an Execute-level action as it triggers an external operation whose effects depend on which release/episode is specified.

From the tool's definition 'Download a specific release for an episode' — triggers an external download operation via Sonarr's API

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

download_release Rate-limited

download_release stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "download_release": {
      "limits": [
        {
          "counter": "download_release_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sonarr MCP Server, so you can run agents against it safely.

FAQ

Questions about download_release

What does the download_release tool do? +

Download a specific release for an episode. It is categorised as a Execute tool in the Sonarr MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on download_release? +

Register the Sonarr MCP Server MCP server in PolicyLayer and add a rule for download_release: 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 Sonarr MCP Server. Nothing to install.

What risk level is download_release? +

download_release is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit download_release? +

Yes. Add a rate_limit block to the download_release 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.

How do I block download_release completely? +

Set action: deny in the PolicyLayer policy for download_release. 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.

What MCP server provides download_release? +

download_release is provided by the Sonarr MCP Server MCP server (micky-devs/sonarr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.