radarr_grab_release · Homelab MCP: Risk & Policy

WHAT IT DOES

What radarr_grab_release does on Homelab

AI agents invoke radarr_grab_release to trigger actions in Homelab. 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 radarr_grab_release needs a policy

This tool initiates an external operation (sending a release to a download client), which constitutes executing an action with side effects beyond simple data retrieval or local data modification. It triggers a download process on an external system, which could consume bandwidth, storage, and potentially involve copyrighted content.

From the tool's definition 'Grab a specific release by its GUID and send it to the download client' — triggers an external download operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

radarr_grab_release Rate-limited

radarr_grab_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": {
    "radarr_grab_release": {
      "limits": [
        {
          "counter": "radarr_grab_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 Homelab, so you can run agents against it safely.

FAQ

Questions about radarr_grab_release

What does the radarr_grab_release tool do? +

Grab a specific release by its GUID (from radarr_interactive_search) and send it to the download client. It is categorised as a Execute tool in the Homelab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on radarr_grab_release? +

Register the Homelab MCP server in PolicyLayer and add a rule for radarr_grab_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 Homelab. Nothing to install.

What risk level is radarr_grab_release? +

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

Can I rate-limit radarr_grab_release? +

Yes. Add a rate_limit block to the radarr_grab_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 radarr_grab_release completely? +

Set action: deny in the PolicyLayer policy for radarr_grab_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 radarr_grab_release? +

radarr_grab_release is provided by the Homelab MCP server (nainounen/homelab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.