Bulk delete selected files from disk and remove them from the database
AI agents call tdarr_bulk_delete_files 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.
This tool irreversibly deletes files from disk and purges records from the database. There is no undo capability for either operation. The bulk nature and lack of granular confirmation per file amplifies the risk. Misuse by an AI agent could result in large-scale data loss. This is Destructive, not just Write.
From the tool's definition 'Bulk delete selected files from disk and remove them from the database' - explicitly states files are deleted from disk (irreversible) and removed from the database (irreversible data removal)
Attacks that exploit this kind of access
Bulk delete selected files from disk and remove them from the database. 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_bulk_delete_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_delete_files 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_bulk_delete_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_delete_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_delete_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 →