crow_delete_file

Permanently delete a file from storage. This cannot be undone. Returns a preview and confirmation token on first call; pass the token back to execute.

SERVERCrow SOURCEkh0pper/crow
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/crow-delete-file.md

What crow_delete_file does on Crow

AI agents call crow_delete_file to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why crow_delete_file is rated Critical

This tool irreversibly deletes data and cannot be undone, making it Destructive rather than Write. The two-step confirmation process (preview + token) mitigates risk somewhat but does not change the fundamental nature of the action.

From the tool's definition Tool description explicitly states 'Permanently delete a file from storage. This cannot be undone.' The name 'crow_delete_file' and the irreversible nature of the operation are clear indicators.

Questions about crow_delete_file

What does the crow_delete_file tool do? +

Permanently delete a file from storage. This cannot be undone. Returns a preview and confirmation token on first call; pass the token back to execute. It is categorised as a Destructive tool in the Crow 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 crow_delete_file? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_delete_file: 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 Crow. Nothing to install.

What risk level is crow_delete_file? +

crow_delete_file 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 crow_delete_file? +

Yes. Add a rate_limit block to the crow_delete_file 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 crow_delete_file completely? +

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

crow_delete_file is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Crow, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Crow's. Pull the full record:

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.