container_file_delete
Delete file in the working directory
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
File deletion cannot be undone and permanently removes data. This is classified as Destructive rather than Write because the operation is not reversible. In a containerized environment, deleting files could impact application state, configuration, or data integrity.
From the tool's definition Tool name 'container_file_delete' and description 'Delete file in the working directory' explicitly perform file deletion, an irreversible operation.
Attacks that exploit this kind of access
The rule that runs container_file_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cloudflare, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For container_file_delete, this is the rule to start with:
container_file_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Cloudflare, apply this rule, and every container_file_delete call is checked against it from then on.
Questions about container_file_delete
Delete 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.
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.
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.
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.
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.
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.
Across the catalogue