tdarr_scan_individual_file · Tdarr MCP: Risk & Policy

WHAT IT DOES

What tdarr_scan_individual_file does on Tdarr

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

Scanning a file with various tools constitutes executing an operation against that file. While it may be read-like in intent, it triggers external tool execution whose effects depend on arguments (which tools are applied). It's not purely read-only since active scanning processes are invoked. Severity is medium as misuse could trigger unintended processing on files in the transcoding system.

From the tool's definition 'Scan an individual file with various tools' — triggers an external scanning/analysis operation on a file

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tdarr_scan_individual_file Rate-limited

tdarr_scan_individual_file 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_scan_individual_file": {
      "limits": [
        {
          "counter": "tdarr_scan_individual_file_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_scan_individual_file

What does the tdarr_scan_individual_file tool do? +

Scan an individual file with various tools. 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_scan_individual_file? +

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

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

Can I rate-limit tdarr_scan_individual_file? +

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

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

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