AI agents use tdarr_save_plugin_text 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 creates or modifies plugin text/configuration in the Tdarr system. While reversible (Write category), it could impact transcoding behavior if malicious code is injected into plugins. Severity is medium because the blast radius is limited to plugin configuration (not system-wide destructive), and effects depend on what code an agent saves.
From the tool's definition Tool name includes 'save' and description states 'Save plugin text for the classic plugin editor', indicating creation or modification of plugin configuration data.
Attacks that exploit this kind of access
Save plugin text for the classic plugin editor. 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_save_plugin_text: 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_save_plugin_text 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_save_plugin_text 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_save_plugin_text. 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_save_plugin_text 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 →