tdarr_update_plugins · Tdarr MCP: Risk & Policy

WHAT IT DOES

What tdarr_update_plugins does on Tdarr

AI agents invoke tdarr_update_plugins 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_update_plugins needs a policy

This tool causes the server to pull and apply updates to community plugins, which is an external operation with side effects beyond simple data writes. It could introduce new or changed plugin behavior affecting transcoding workflows. It's not purely destructive or financial, but it executes an update process that modifies server state in ways that may be difficult to reverse (e.g., overwriting plugin versions).

From the tool's definition 'update community plugins' — triggers an external operation on the server to fetch and apply plugin updates

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tdarr_update_plugins Rate-limited

tdarr_update_plugins 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_update_plugins": {
      "limits": [
        {
          "counter": "tdarr_update_plugins_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_update_plugins

What does the tdarr_update_plugins tool do? +

Request the server to update community plugins. 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_update_plugins? +

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

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

Can I rate-limit tdarr_update_plugins? +

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

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

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