tdarr_sync_plugins · Tdarr MCP: Risk & Policy

WHAT IT DOES

What tdarr_sync_plugins does on Tdarr

AI agents invoke tdarr_sync_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_sync_plugins needs a policy

This tool triggers an external operation that distributes plugin files across all nodes in a distributed transcoding system. It is not a simple read or write — it actively pushes/deploys content to multiple remote systems, which is an Execute-class action. Misuse could cause all nodes to load incorrect or malicious plugins, affecting the entire transcoding cluster.

From the tool's definition Sync plugins from server to all nodes

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tdarr_sync_plugins Rate-limited

tdarr_sync_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_sync_plugins": {
      "limits": [
        {
          "counter": "tdarr_sync_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_sync_plugins

What does the tdarr_sync_plugins tool do? +

Sync plugins from server to all nodes. 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_sync_plugins? +

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

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

Can I rate-limit tdarr_sync_plugins? +

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

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

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

// THE FULL RECORD

tdarr_sync_plugins is one line of Tdarr's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →