AI agents invoke tdarr_transcode_user_verdict 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.
This tool executes an action (verdict/decision) on a staged transcoding item, which triggers processing operations. It's not simply reading data, and the action taken could initiate resource-intensive transcoding jobs or approve/reject file processing. The description is vague but 'take action' implies execution of an operation rather than a simple write or read.
From the tool's definition 'Take action on a staged item' — triggers an action on a transcoding item that is staged/queued in the Tdarr pipeline
Attacks that exploit this kind of access
Take action on a staged item. 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_transcode_user_verdict: 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_transcode_user_verdict 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_transcode_user_verdict 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_transcode_user_verdict. 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_transcode_user_verdict 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 →