tdarr_scan_files · Tdarr MCP: Risk & Policy

WHAT IT DOES

What tdarr_scan_files does on Tdarr

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

This tool executes scan operations against a Tdarr library, which triggers active file system scanning processes. It is not a simple read/query since it initiates background operations whose effects depend on arguments (scan type and dbID). It falls under Execute as it runs external operations, with medium severity since misuse could trigger unintended large-scale scans but does not directly destroy or modify data.

From the tool's definition 'Run a scanFresh, scanFindNew or scanFolderWatcher on a library' — triggers external scanning operations on a library

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tdarr_scan_files Rate-limited

tdarr_scan_files 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_files": {
      "limits": [
        {
          "counter": "tdarr_scan_files_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_files

What does the tdarr_scan_files tool do? +

Run a scanFresh, scanFindNew or scanFolderWatcher on a library. scanFresh & scanFindNew require a single string dbID inside scanConfig. 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_files? +

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

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

Can I rate-limit tdarr_scan_files? +

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

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

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