radarr_blocklist_release · Homelab MCP: Risk & Policy

WHAT IT DOES

What radarr_blocklist_release does on Homelab

AI agents use radarr_blocklist_release to create or update resources in Homelab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Homelab environment.

WHY IT NEEDS A POLICY

Why radarr_blocklist_release needs a policy

Blocklisting a release modifies Radarr's blocklist data (marking a release as bad) and may trigger a search operation. This is a reversible write action — blocklists can typically be managed/removed — though it does affect the download queue state. The optional fresh search is an external trigger but secondary to the write action.

From the tool's definition Blocklist a specific bad release from the Radarr queue and optionally trigger a fresh search

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

radarr_blocklist_release Rate-limited

radarr_blocklist_release stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_blocklist_release": {
      "limits": [
        {
          "counter": "radarr_blocklist_release_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_blocklist_release

What does the radarr_blocklist_release tool do? +

Blocklist a specific bad release from the Radarr queue and optionally trigger a fresh search. Use queue_id from radarr_get_queue. It is categorised as a Write tool in the Homelab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on radarr_blocklist_release? +

Register the Homelab MCP server in PolicyLayer and add a rule for radarr_blocklist_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_blocklist_release? +

radarr_blocklist_release is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit radarr_blocklist_release? +

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

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

radarr_blocklist_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.