sandbox_ports_expose

Run sandbox-ports.expose through the Appaloft application operation catalog. Shared with CLI and HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp
High RISK CLASS
Category Execute
Parameters 42 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

sandbox_ports_expose triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Questions about sandbox_ports_expose

What does the sandbox_ports_expose tool do? +

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.

What parameters does sandbox_ports_expose accept? +

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.

How do I enforce a policy on sandbox_ports_expose? +

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.

What risk level is sandbox_ports_expose? +

sandbox_ports_expose is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sandbox_ports_expose? +

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.

How do I block sandbox_ports_expose completely? +

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.

What MCP server provides sandbox_ports_expose? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Appaloft's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.