sandbox_ports_expose
Run sandbox-ports.expose through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/sandbox-ports-expose.md
What sandbox_ports_expose does on Appaloft
AI agents invoke sandbox_ports_expose to trigger actions in Appaloft. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
port | integer | Yes | |
expiresAt | string | — | |
sandboxId | string | Yes | |
visibility | string | — |
Parameters from the server's own tool schema.
Why sandbox_ports_expose is rated High
This tool triggers execution of a sandbox port exposure operation, which is a system-level action with external effects (modifying network access/routing). It is not a simple read (no query semantics), not a write in the traditional data sense, and not destructive or financial.
From the tool's definition Tool name 'sandbox_ports_expose' indicates an operation that exposes ports in a sandbox environment. Description states it 'Run[s] sandbox-ports.expose through the Appaloft application operation catalog,' indicating execution of an external operation.
Attacks that exploit this kind of access
The rule that runs sandbox_ports_expose safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sandbox_ports_expose, this is the rule to start with:
sandbox_ports_expose 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 Appaloft, apply this rule, and every sandbox_ports_expose call is checked against it from then on.
Questions about sandbox_ports_expose
Run sandbox-ports.expose through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
sandbox_ports_expose accepts 4 parameters: port, expiresAt, sandboxId, visibility. Required: port, sandboxId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for sandbox_ports_expose: 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 Appaloft. Nothing to install.
sandbox_ports_expose 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_ports_expose 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_ports_expose. 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_ports_expose is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue