tdarr_delete_unhealthy_files

Delete files which have failed to transcode (table3) or unhealthy files (table6)

Server Tdarr maximeallanic/tdarr-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What tdarr_delete_unhealthy_files does on Tdarr

AI agents call tdarr_delete_unhealthy_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.

Why tdarr_delete_unhealthy_files needs a policy

This tool permanently removes files from the system based on transcoding status or health criteria. Deletion is irreversible and represents data loss. While the blast radius is somewhat bounded (only targets unhealthy/failed files rather than arbitrary selections), the destructive nature and potential for unintended file loss (if health criteria are incorrectly applied or misunderstood) warrant high severity.

From the tool's definition Tool name explicitly contains "delete" and description states "Delete files which have failed to transcode (table3) or unhealthy files (table6)" — this is an irreversible deletion operation.

Questions about tdarr_delete_unhealthy_files

What does the tdarr_delete_unhealthy_files tool do? +

Delete files which have failed to transcode (table3) or unhealthy files (table6). 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.

How do I enforce a policy on tdarr_delete_unhealthy_files? +

Register the Tdarr MCP server in PolicyLayer and add a rule for tdarr_delete_unhealthy_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.

What risk level is tdarr_delete_unhealthy_files? +

tdarr_delete_unhealthy_files is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit tdarr_delete_unhealthy_files? +

Yes. Add a rate_limit block to the tdarr_delete_unhealthy_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.

How do I block tdarr_delete_unhealthy_files completely? +

Set action: deny in the PolicyLayer policy for tdarr_delete_unhealthy_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.

What MCP server provides tdarr_delete_unhealthy_files? +

tdarr_delete_unhealthy_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.