# 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

Agent View of the PolicyLayer registry record for `runbox_write_file`. HTML page: https://policylayer.com/tools/11cafe-website-publisher-mcp/runbox-write-file

## Facts

- Tool: `runbox_write_file`
- Server: Runbox Website Builder MCP (`11cafe/website-publisher-mcp`) — https://policylayer.com/tools/11cafe-website-publisher-mcp.md
- Homepage: https://github.com/11cafe/website-publisher-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "runbox_write_file",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Runbox Website Builder MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "runbox_write_file": {
      "limits": [
        {
          "counter": "runbox_write_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Runbox Website Builder MCP (6)

- `runbox_create_sandbox` — Execute — https://policylayer.com/tools/11cafe-website-publisher-mcp/runbox-create-sandbox.md
- `runbox_execute_command` — Execute — https://policylayer.com/tools/11cafe-website-publisher-mcp/runbox-execute-command.md
- `runbox_expose_port` — Execute — https://policylayer.com/tools/11cafe-website-publisher-mcp/runbox-expose-port.md
- `runbox_serve_static_website` — Execute — https://policylayer.com/tools/11cafe-website-publisher-mcp/runbox-serve-static-website.md
- `runbox_list_directory` — Read — https://policylayer.com/tools/11cafe-website-publisher-mcp/runbox-list-directory.md
- `runbox_read_file` — Read — https://policylayer.com/tools/11cafe-website-publisher-mcp/runbox-read-file.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=11cafe-website-publisher-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/11cafe-website-publisher-mcp