prowlarr_test_indexers · Homelab MCP: Risk & Policy

WHAT IT DOES

What prowlarr_test_indexers does on Homelab

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

Testing indexers involves making outbound network requests to external services, which constitutes executing an external operation. It is not purely reading local data; it actively probes remote endpoints. No data is created or destroyed, but the external trigger elevates this above a simple Read.

From the tool's definition 'Test all indexers (or a specific one) in Prowlarr to verify they are working' — triggers an external operation (network connectivity test against remote indexer endpoints)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

prowlarr_test_indexers Rate-limited

prowlarr_test_indexers 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": {
    "prowlarr_test_indexers": {
      "limits": [
        {
          "counter": "prowlarr_test_indexers_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 prowlarr_test_indexers

What does the prowlarr_test_indexers tool do? +

Test all indexers (or a specific one) in Prowlarr to verify they are working. 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 prowlarr_test_indexers? +

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

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

Can I rate-limit prowlarr_test_indexers? +

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

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

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