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
This record as markdown: /tools/11cafe-website-publisher-mcp/runbox-expose-port.md
What runbox_expose_port does on Runbox Website Builder MCP
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.
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 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'
Attacks that exploit this kind of access
The rule that runs runbox_expose_port 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_expose_port, this is the rule to start with:
runbox_expose_port stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_expose_port call is checked against it from then on.
Questions about 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. It is categorised as a Execute tool in the Runbox Website Builder MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Runbox Website Builder MCP server in PolicyLayer and add a rule for runbox_expose_port: 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_expose_port is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the runbox_expose_port 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_expose_port. 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_expose_port 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.
Across the catalogue