AI agents invoke tdarr_get_new_task 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.
Requesting a new task causes the Tdarr system to assign and begin executing a transcoding operation on a node. This is an external operation that triggers active processing (transcoding), making it Execute rather than a simple Read. Misuse could cause unintended transcoding jobs to start, consuming resources or processing files unexpectedly.
From the tool's definition 'Request a new task for a node' — triggers the assignment and initiation of a new transcoding task on a worker node
Attacks that exploit this kind of access
Request a new task for a 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.
Register the Tdarr MCP server in PolicyLayer and add a rule for tdarr_get_new_task: 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_get_new_task 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_get_new_task 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_get_new_task. 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_get_new_task 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 →