sonarr_season_search · Homelab MCP: Risk & Policy

WHAT IT DOES

What sonarr_season_search does on Homelab

AI agents invoke sonarr_season_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_season_search needs a policy

This tool triggers an active search operation in Sonarr, which causes the application to query indexers and potentially initiate downloads of media content. It's not a passive read — it executes an external operation (search + possible download trigger) against the Sonarr service, making it Execute category. Misuse could result in unwanted downloads consuming storage or bandwidth.

From the tool's definition Search for a specific season of a series in Sonarr

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sonarr_season_search Rate-limited

sonarr_season_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_season_search": {
      "limits": [
        {
          "counter": "sonarr_season_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_season_search

What does the sonarr_season_search tool do? +

Search for a specific season of a series in Sonarr. 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_season_search? +

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

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

Can I rate-limit sonarr_season_search? +

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

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

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