Remove all files from a Tdarr library DB (files on disk are not removed)
AI agents call tdarr_remove_library_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 removes all file records from a library database. Although the description clarifies that files on disk are not removed, wiping all entries from a library DB is an irreversible bulk deletion of data (the database records), making it Destructive. The blast radius is high because removing all library records could require a full re-scan to rebuild and may disrupt ongoing transcoding operations.
From the tool's definition Remove all files from a Tdarr library DB
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Remove all files from a Tdarr library DB (files on disk are not removed). 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_library_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_remove_library_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_remove_library_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_remove_library_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_remove_library_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 →