# runbox_expose_port

Expose a port in a Runbox code sandbox to the public internet for user testing. It returns a url that can access your local running web server at 0.0.0.0:port in your sandbox

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

## Facts

- Tool: `runbox_expose_port`
- 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: Execute (High 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_expose_port",
    "arguments": {}
  }
}
```

## Why runbox_expose_port is rated High

This tool triggers an external network operation that makes an internal sandbox service publicly accessible on the internet. It is not merely reading data or writing files — it actively changes network exposure and creates a public URL endpoint.

From the tool's own definition: "'Expose a port in a Runbox code sandbox to the public internet' and 'returns a url that can access your local running web server'"

## Use case

AI agents invoke runbox_expose_port to trigger actions in Runbox Website Builder MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## 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_expose_port": {
      "limits": [
        {
          "counter": "runbox_expose_port_rate",
          "window": "minute",
          "max": 10,
          "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_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
- `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