tdarr_kill_file_scanner · Tdarr MCP: Risk & Policy

WHAT IT DOES

What tdarr_kill_file_scanner does on Tdarr

AI agents invoke tdarr_kill_file_scanner to trigger actions in Tdarr. 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 tdarr_kill_file_scanner needs a policy

This tool terminates an active process (file scanner), which is an execution control action. It forcibly stops an in-progress operation, which could disrupt scanning workflows and lose intermediate state, but does not permanently delete data. 'Kill' implies terminating a running process, categorizing it as Execute rather than Destructive since file data itself is not removed.

From the tool's definition Kill a file scanner in progress

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tdarr_kill_file_scanner Rate-limited

tdarr_kill_file_scanner 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": {
    "tdarr_kill_file_scanner": {
      "limits": [
        {
          "counter": "tdarr_kill_file_scanner_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 Tdarr, so you can run agents against it safely.

FAQ

Questions about tdarr_kill_file_scanner

What does the tdarr_kill_file_scanner tool do? +

Kill a file scanner in progress. It is categorised as a Execute tool in the Tdarr MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tdarr_kill_file_scanner? +

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

What risk level is tdarr_kill_file_scanner? +

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

Can I rate-limit tdarr_kill_file_scanner? +

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

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

tdarr_kill_file_scanner is provided by the Tdarr MCP server (maximeallanic/tdarr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.