sonarr_force_search · Homelab MCP: Risk & Policy

WHAT IT DOES

What sonarr_force_search does on Homelab

AI agents invoke sonarr_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 sonarr_force_search needs a policy

This tool triggers an external operation (searching all indexers via Sonarr) that causes network activity and potentially initiates downloads. It doesn't merely read data—it actively forces a search action across multiple indexers, which is an external operation with side effects. It's not purely destructive or financial, making Execute the most appropriate category.

From the tool's definition Force Sonarr to search all indexers for missing episodes

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sonarr_force_search Rate-limited

sonarr_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": {
    "sonarr_force_search": {
      "limits": [
        {
          "counter": "sonarr_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 sonarr_force_search

What does the sonarr_force_search tool do? +

Force Sonarr to search all indexers for missing episodes of a series. 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 sonarr_force_search? +

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

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

Can I rate-limit sonarr_force_search? +

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

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

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