Delete a backup of the Tdarr database
AI agents call tdarr_delete_backup 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 performs an irreversible deletion operation on database backups. While not directly deleting production data, destroying backups eliminates recovery options and could prevent disaster recovery. This is categorized as Destructive rather than Write because backups cannot be easily recreated and their loss cannot be undone without external restoration processes.
From the tool's definition Tool name explicitly states 'delete_backup' and description confirms it 'Delete a backup of the Tdarr database'. The action irreversibly removes a backup copy of critical system data.
Attacks that exploit this kind of access
Delete a backup of the Tdarr 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_delete_backup: 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_delete_backup 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_delete_backup 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_delete_backup. 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_delete_backup 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 →