sandboxes_create
Run sandboxes.create through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/sandboxes-create.md
What sandboxes_create does on Appaloft
AI agents invoke sandboxes_create 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 |
|---|---|---|---|
limits | object | Yes | |
source | object | Yes | |
expiresAt | string | — | |
providerKey | string | — | |
networkPolicy | object | Yes | |
requestedIsolation | string | Yes |
Parameters from the server's own tool schema.
Why sandboxes_create is rated High
Creating a sandbox implies provisioning and executing an isolated runtime environment. This is an Execute-class action with a high blast radius since it spins up compute resources. The description is sparse, so confidence is moderate, but 'run' and 'sandboxes.create' together strongly suggest execution of an environment rather than a simple data write.
From the tool's definition 'Run sandboxes.create through the Appaloft application operation catalog' — creates and runs a sandbox environment
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs sandboxes_create 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 sandboxes_create, this is the rule to start with:
sandboxes_create 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 sandboxes_create call is checked against it from then on.
Questions about sandboxes_create
Run sandboxes.create 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.
sandboxes_create accepts 6 parameters: limits, source, expiresAt, providerKey, networkPolicy, requestedIsolation. Required: limits, source, networkPolicy, requestedIsolation. 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 sandboxes_create: 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.
sandboxes_create 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 sandboxes_create 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 sandboxes_create. 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.
sandboxes_create 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