AI agents use tdarr_bulk_update_files 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 file metadata or properties in the Tdarr transcoding system without permanently deleting data. The bulk operation on files carries significant blast radius—an AI agent could inadvertently alter metadata, properties, or states for large numbers of files—but remains in the Write category since updates are typically reversible.
From the tool's definition Tool name 'tdarr_bulk_update_files' combined with description 'Bulk update specific files by their IDs' indicates modification of data at scale. The 'bulk' qualifier and 'update' verb confirm reversible write operations on multiple file records.
Attacks that exploit this kind of access
Bulk update specific files by their IDs. 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_bulk_update_files: 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_bulk_update_files 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_bulk_update_files 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_bulk_update_files. 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_bulk_update_files 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 →