New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

container_file_delete

Delete a file in the working directory.

SERVERCloudflare SOURCEhttps://builds.mcp.cloudflare.com/sse
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/cloudflare/container-file-delete.md

What container_file_delete does on Cloudflare

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

Why container_file_delete is rated Critical

Deleting a file is an irreversible operation that cannot be undone. This falls squarely into the Destructive category. Severity is high because an AI agent could accidentally or maliciously remove critical files, though the impact is limited to the container's working directory rather than production systems. Confidence is high due to explicit use of 'delete' in both name and description.

From the tool's definition Tool name is 'container_file_delete' and description states 'Delete a file in the working directory.' The verb 'delete' is explicitly destructive.

Questions about container_file_delete

What does the container_file_delete tool do? +

Delete a file in the working directory. It is categorised as a Destructive tool in the Cloudflare 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 container_file_delete? +

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

What risk level is container_file_delete? +

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

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

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

container_file_delete is provided by the Cloudflare MCP server (https://builds.mcp.cloudflare.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Cloudflare, 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 Cloudflare'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.