radarr_force_search · Homelab MCP: Risk & Policy

WHAT IT DOES

What radarr_force_search does on Homelab

AI agents invoke radarr_force_search 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_force_search needs a policy

This tool triggers an external operation (searching all indexers via Radarr) rather than simply reading data or writing/modifying records. It initiates active network requests to multiple indexers, potentially causing side effects like triggering download queue entries or rate-limiting on indexer services. It falls under Execute as it runs an external operation whose effects depend on what is found.

From the tool's definition Force Radarr to search all indexers for a specific movie

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

radarr_force_search Rate-limited

radarr_force_search 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_force_search": {
      "limits": [
        {
          "counter": "radarr_force_search_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_force_search

What does the radarr_force_search tool do? +

Force Radarr to search all indexers for a specific movie already in the library. 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_force_search? +

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

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

Can I rate-limit radarr_force_search? +

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

Set action: deny in the PolicyLayer policy for radarr_force_search. 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_force_search? +

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