container_file_write
Create a file with the provided contents in the working directory, overwriting it if it exists.
This record as markdown: /tools/cloudflare/container-file-write.md
What container_file_write does on Cloudflare
AI agents use container_file_write to create or update resources in Cloudflare, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cloudflare environment.
Why container_file_write is rated Medium
This tool creates or modifies files, which is a Write operation. It is reversible (files can be edited or deleted afterward), so it does not meet the Destructive threshold. Severity is high because uncontrolled file writing in a container could corrupt application state, configurations, or inject malicious content, but the impact is scoped to the container filesystem and reversible.
From the tool's definition Tool description explicitly states: 'Create a file with the provided contents in the working directory, overwriting it if it exists.' The tool modifies data (file creation/overwriting) in a reversible manner.
Attacks that exploit this kind of access
The rule that runs container_file_write 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_write, this is the rule to start with:
container_file_write stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cloudflare, apply this rule, and every container_file_write call is checked against it from then on.
Questions about container_file_write
Create a file with the provided contents in the working directory, overwriting it if it exists. It is categorised as a Write tool in the Cloudflare MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cloudflare MCP server in PolicyLayer and add a rule for container_file_write: 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_write is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the container_file_write 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_write. 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_write 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.
This server
Across the catalogue