AI agents use tdarr_toggle_schedule 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 library scheduling configuration, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary operations (Execute), involve financial transactions (Financial), or merely read state (Read). The blast radius is medium because misconfiguring transcoding schedules could disrupt media processing workflows, but the change can be undone by toggling the schedule again.
From the tool's definition Tool name 'tdarr_toggle_schedule' and description 'Update the schedule of a library' indicate modification of configuration state. The word 'Update' is key—this creates or modifies data reversibly (a schedule can be toggled back).
Attacks that exploit this kind of access
Update the schedule of a library. 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_toggle_schedule: 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_toggle_schedule 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_toggle_schedule 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_toggle_schedule. 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_toggle_schedule 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 →