runbox_serve_static_website
Serve a static website in a Runbox code sandbox. Just write all your static html, css, js files to the sandbox. You will get a url to access your website. Must have a ./index.html file in the sandbox root directory.
This record as markdown: /tools/11cafe-website-publisher-mcp/runbox-serve-static-website.md
What runbox_serve_static_website does on Runbox Website Builder MCP
AI agents invoke runbox_serve_static_website 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_serve_static_website is rated High
This tool starts a web server process inside a sandbox and exposes it as a live URL, which constitutes triggering an external operation (serving content publicly). While it doesn't execute arbitrary code directly, it activates a runtime service that makes sandbox contents publicly accessible.
From the tool's definition 'Serve a static website in a Runbox code sandbox' and 'You will get a url to access your website' — triggers an external serving operation that exposes files via a live public URL
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs runbox_serve_static_website 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_serve_static_website, this is the rule to start with:
runbox_serve_static_website 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_serve_static_website call is checked against it from then on.
Questions about runbox_serve_static_website
Serve a static website in a Runbox code sandbox. Just write all your static html, css, js files to the sandbox. You will get a url to access your website. Must have a ./index.html file in the sandbox root directory. 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_serve_static_website: 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_serve_static_website 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_serve_static_website 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_serve_static_website. 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_serve_static_website 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