tdarr_run_automation · Tdarr MCP: Risk & Policy

WHAT IT DOES

What tdarr_run_automation does on Tdarr

AI agents invoke tdarr_run_automation 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_run_automation needs a policy

Triggering automations in a distributed transcoding system can initiate resource-intensive operations, file processing, or queue modifications. The effects are not immediately reversible and depend entirely on the automation's configuration. This fits the Execute category: the tool runs operations triggered by arguments (which automation to run), and the consequences are determined by that automation's logic.

From the tool's definition Tool name 'tdarr_run_automation' combined with description 'Manually trigger an automation' indicates the tool executes pre-configured automation workflows whose effects depend on what those automations do (transcoding jobs, file operations, etc.).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tdarr_run_automation Rate-limited

tdarr_run_automation 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_run_automation": {
      "limits": [
        {
          "counter": "tdarr_run_automation_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_run_automation

What does the tdarr_run_automation tool do? +

Manually trigger an automation. 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_run_automation? +

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

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

Can I rate-limit tdarr_run_automation? +

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

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

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