AI agents invoke tdarr_restart_ui 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.
Restarting a UI is an execute action that triggers an external operation on the Tdarr system. While not destructive (data is not lost) or financial, it disrupts service availability and falls under Execute rather than Write. The medium severity reflects that UI restart causes temporary service interruption but does not cause data loss or financial impact.
From the tool's definition Tool name 'tdarr_restart_ui' and description 'Restart the Tdarr UI' indicate execution of a service restart operation. This is an external system operation with side effects that cannot be precisely controlled by argument variation.
Attacks that exploit this kind of access
Restart the Tdarr UI. 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.
Register the Tdarr MCP server in PolicyLayer and add a rule for tdarr_restart_ui: 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.
tdarr_restart_ui is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tdarr_restart_ui 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.
Set action: deny in the PolicyLayer policy for tdarr_restart_ui. 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.
tdarr_restart_ui 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →