# runbox_read_file

Read the content of a file from an existing Runbox linux sandbox

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

## Facts

- Tool: `runbox_read_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: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why runbox_read_file is rated Low

This tool retrieves file contents from a sandbox environment without side effects. It is a straightforward read operation analogous to 'cat' or 'get' commands. While the sandbox context involves a coding environment, this specific tool only accesses data and does not execute, modify, or delete anything.

From the tool's own definition: "Tool name and description explicitly state 'Read the content of a file' with no modification, deletion, or execution capabilities."

## Use case

AI agents call runbox_read_file to retrieve information from Runbox Website Builder MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. 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_read_file": {}
  }
}
```

## 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_write_file` — Write — https://policylayer.com/tools/11cafe-website-publisher-mcp/runbox-write-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