prowlarr_test_indexer · Nas MCP: Risk & Policy

WHAT IT DOES

What prowlarr_test_indexer does on Nas

AI agents invoke prowlarr_test_indexer to trigger actions in Nas. 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_indexer needs a policy

This tool triggers an external operation — testing a connection to an indexer — which involves making a live network request to an external service. It doesn't merely read local data; it actively initiates an outbound connection. This falls under Execute as it triggers an external operation whose effects depend on the target indexer argument.

From the tool's definition "Teste la connexion à un indexeur spécifique" (Tests the connection to a specific indexer)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

prowlarr_test_indexer Rate-limited

prowlarr_test_indexer 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_indexer": {
      "limits": [
        {
          "counter": "prowlarr_test_indexer_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 Nas, so you can run agents against it safely.

FAQ

Questions about prowlarr_test_indexer

What does the prowlarr_test_indexer tool do? +

Teste la connexion à un indexeur spécifique. It is categorised as a Execute tool in the Nas 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_indexer? +

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

What risk level is prowlarr_test_indexer? +

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

Can I rate-limit prowlarr_test_indexer? +

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

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

prowlarr_test_indexer is provided by the Nas MCP server (matthieurosset/nas-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.