AI agents use tdarr_update_plugin_include to create or update resources in Tdarr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tdarr environment.
This tool modifies plugin settings within the Tdarr transcoding system. Enabling/disabling plugins affects which transcoding operations are performed, but the change is reversible (plugins can be re-enabled or disabled). This is a Write operation as it creates or modifies configuration data without permanently destroying data or executing arbitrary code.
From the tool's definition Tool description states 'Enable/disable a plugin in a classic plugin stack' — this modifies plugin configuration state (enables or disables plugins), which is a reversible configuration change.
Attacks that exploit this kind of access
Enable/disable a plugin in a classic plugin stack. It is categorised as a Write tool in the Tdarr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tdarr MCP server in PolicyLayer and add a rule for tdarr_update_plugin_include: 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_update_plugin_include is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tdarr_update_plugin_include 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_update_plugin_include. 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_update_plugin_include 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 →