Remove a plugin from a classic plugin stack
AI agents call tdarr_remove_plugin_include to permanently remove resources in Tdarr — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a plugin from a stack is a destructive configuration change that cannot be trivially undone without knowing the previous state. This modifies the processing pipeline, potentially causing videos to be processed differently or skipping transcoding steps. While not as severe as deleting files, it irreversibly alters the plugin stack configuration.
From the tool's definition 'Remove a plugin from a classic plugin stack' — permanently removes a plugin entry from the stack configuration
Attacks that exploit this kind of access
Remove a plugin from a classic plugin stack. It is categorised as a Destructive tool in the Tdarr MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tdarr MCP server in PolicyLayer and add a rule for tdarr_remove_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_remove_plugin_include is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the tdarr_remove_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_remove_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_remove_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 →