tdarr_restart_node · Tdarr MCP: Risk & Policy

WHAT IT DOES

What tdarr_restart_node does on Tdarr

AI agents invoke tdarr_restart_node 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_restart_node needs a policy

Restarting a node is an Execute-class action because it triggers an external operation on infrastructure. While not destructive (data is not deleted), and not financial, the blast radius is significant: an unintended restart could disrupt active transcoding jobs, impact service availability, and require manual recovery.

From the tool's definition Tool name and description: 'tdarr_restart_node: Restart a specific node'. The action of restarting a node is an external operation that triggers system-level effects (shutdown and reboot of a worker node in the distributed transcoding system).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tdarr_restart_node Rate-limited

tdarr_restart_node 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_restart_node": {
      "limits": [
        {
          "counter": "tdarr_restart_node_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_restart_node

What does the tdarr_restart_node tool do? +

Restart a specific node. 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_restart_node? +

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

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

Can I rate-limit tdarr_restart_node? +

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

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

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