sandbox_expose_raw_port
Expose a RAW layer-4 (TCP/UDP) port of the sandbox — the only way to reach a service that does not speak HTTP (SSH on 22, media/UDP). NOT needed for WebSocket: wss:// works over sandbox_expose_port, which serves layer 7 (HTTP + WS) and rejects only 22/23/25/445/3389. Returns { hostPort, guestPort...
This record as markdown: /tools/cloud-easybits-easybits/sandbox-expose-raw-port.md
What sandbox_expose_raw_port does on EasyBits
AI agents invoke sandbox_expose_raw_port to trigger actions in EasyBits. 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 sandbox_expose_raw_port is rated High
Exposes raw network ports, enabling external access to sandbox services with broad attack surface.
From the tool's definition Expose a RAW layer-4 (TCP/UDP) port of the sandbox
Attacks that exploit this kind of access
The rule that runs sandbox_expose_raw_port safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sandbox_expose_raw_port, this is the rule to start with:
sandbox_expose_raw_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 EasyBits, apply this rule, and every sandbox_expose_raw_port call is checked against it from then on.
Questions about sandbox_expose_raw_port
Expose a RAW layer-4 (TCP/UDP) port of the sandbox — the only way to reach a service that does not speak HTTP (SSH on 22, media/UDP). NOT needed for WebSocket: wss:// works over sandbox_expose_port, which serves layer 7 (HTTP + WS) and rejects only 22/23/25/445/3389. Returns { hostPort, guestPort, protocol, host, endpoint }: dial. It is categorised as a Execute tool in the EasyBits MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the EasyBits MCP server in PolicyLayer and add a rule for sandbox_expose_raw_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 EasyBits. Nothing to install.
sandbox_expose_raw_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 sandbox_expose_raw_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 sandbox_expose_raw_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.
sandbox_expose_raw_port is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
Across the catalogue