runbox_write_file
Create a new file or overwrite an existing file in a Runbox linux sandbox. Will return a url to view the file in the sandbox, please display it to the user
What runbox_write_file does on Runbox Website Builder MCP
AI agents use runbox_write_file to create or update resources in Runbox Website Builder MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Runbox Website Builder MCP environment.
Why runbox_write_file is rated Medium
This tool modifies files within a sandbox environment - it can create new files or overwrite existing ones. While file modifications are typically reversible (files can be deleted or restored), the ability to overwrite existing files with arbitrary content poses a high risk in an agent context, as it could corrupt configuration files, website content, or other critical assets.
From the tool's definition Tool description explicitly states: "Create a new file or overwrite an existing file in a Runbox linux sandbox." The verb "write" combined with "create" and "overwrite" indicates reversible modification of data.
Attacks that exploit this kind of access
The rule that runs runbox_write_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Runbox Website Builder MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runbox_write_file, this is the rule to start with:
runbox_write_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Runbox Website Builder MCP, apply this rule, and every runbox_write_file call is checked against it from then on.
Questions about runbox_write_file
Create a new file or overwrite an existing file in a Runbox linux sandbox. Will return a url to view the file in the sandbox, please display it to the user. It is categorised as a Write tool in the Runbox Website Builder MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Runbox Website Builder MCP server in PolicyLayer and add a rule for runbox_write_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 Runbox Website Builder MCP. Nothing to install.
runbox_write_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 runbox_write_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 runbox_write_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.
runbox_write_file is provided by the Runbox Website Builder MCP server (11cafe/website-publisher-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Runbox Website Builder, and thousands of servers like it.
This server
Across the catalogue