prowlarr.indexer_test_all · Arr Stack MCP: Risk & Policy

WHAT IT DOES

What prowlarr.indexer_test_all does on Arr Stack

AI agents invoke prowlarr.indexer_test_all to trigger actions in Arr Stack. 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.indexer_test_all needs a policy

Based on the name, this tool likely triggers an external operation that tests all configured Prowlarr indexers by making network requests to each one. This falls under Execute as it triggers external operations. Severity is medium since misuse could cause rate-limiting or temporary bans from indexers, but no data is modified or deleted. Confidence is low due to empty description.

From the tool's definition Tool name contains 'test_all', suggesting it triggers a test operation against all indexers. Description is empty and uninformative, lowering confidence.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

prowlarr.indexer_test_all Rate-limited

prowlarr.indexer_test_all 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.indexer_test_all": {
      "limits": [
        {
          "counter": "prowlarr.indexer_test_all_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 Arr Stack, so you can run agents against it safely.

FAQ

Questions about prowlarr.indexer_test_all

What does the prowlarr.indexer_test_all tool do? +

prowlarr.indexer_test_all. It is categorised as a Execute tool in the Arr Stack 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.indexer_test_all? +

Register the Arr Stack MCP server in PolicyLayer and add a rule for prowlarr.indexer_test_all: 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 Arr Stack. Nothing to install.

What risk level is prowlarr.indexer_test_all? +

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

Can I rate-limit prowlarr.indexer_test_all? +

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

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

prowlarr.indexer_test_all is provided by the Arr Stack MCP server (new-usemame/arr-stack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.