sandboxes_terminate
Run sandboxes.terminate through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/sandboxes-terminate.md
What sandboxes_terminate does on Appaloft
AI agents call sandboxes_terminate to permanently remove resources in Appaloft, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
sandboxId | string | Yes |
Parameters from the server's own tool schema.
Why sandboxes_terminate is rated Critical
Terminating a sandbox is a destructive, likely irreversible action that destroys the running environment and any ephemeral state within it. The word 'terminate' strongly implies permanent cessation rather than a reversible pause or stop. High severity because misuse could destroy active development or testing environments.
From the tool's definition sandboxes_terminate — 'terminate' indicates irreversible shutdown/destruction of sandbox environments
Attacks that exploit this kind of access
The rule that runs sandboxes_terminate 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_terminate, this is the rule to start with:
sandboxes_terminate is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every sandboxes_terminate call is checked against it from then on.
Questions about sandboxes_terminate
Run sandboxes.terminate through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Destructive tool in the Appaloft MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
sandboxes_terminate accepts 1 parameter: sandboxId. Required: 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 sandboxes_terminate: 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_terminate is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sandboxes_terminate 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_terminate. 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_terminate 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