Create a new file with content in the container. Args: description: Why I'm creating this file. ALWAYS PROVIDE THIS PARAMETER FIRST. file_text: Content to write to the file. ALWAYS PROVIDE THIS PARAMETER SECOND. path: Path to the file to create. ALWAYS PROVIDE THIS PARAMETER LAST. Returns: Succes...
AI agents use create_file to create or update resources in Open Computer Use — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Open Computer Use environment.
This is a Write operation because it creates new files in the container environment—a reversible action. Severity is medium because while file creation is generally benign, an AI agent could misuse this to create malicious scripts, configuration files, or large files that consume resources. The managed Docker container environment provides some isolation, lowering it from high.
From the tool's definition Tool creates a new file with content in a container. Description explicitly states it creates a file and takes file_text as a parameter to write content, classifying it as a reversible data modification operation.
Documented attack patterns abuse exactly the kind of access create_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Open Computer Use, and nothing reaches the server without passing your rules. This is the rule we recommend for create_file:
{
"version": "1",
"default": "deny",
"tools": {
"create_file": {
"limits": [
{
"counter": "create_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_file 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.
Free to start. No card required.
Create a new file with content in the container. Args: description: Why I'm creating this file. ALWAYS PROVIDE THIS PARAMETER FIRST. file_text: Content to write to the file. ALWAYS PROVIDE THIS PARAMETER SECOND. path: Path to the file to create. ALWAYS PROVIDE THIS PARAMETER LAST. Returns: Success message or error. It is categorised as a Write tool in the Open Computer Use MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Open Computer Use MCP server in PolicyLayer and add a rule for create_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 Open Computer Use. Nothing to install.
create_file 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_file is provided by the Open Computer Use MCP server (wide-moat/open-computer-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Open Computer Use tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Open Computer Use tools catalogued and risk-classified — across an index of 42,500+ MCP servers.