sandbox_templates_delete
Run sandbox-templates.delete through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/sandbox-templates-delete.md
What sandbox_templates_delete does on Appaloft
AI agents call sandbox_templates_delete 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 |
|---|---|---|---|
templateId | string | Yes |
Parameters from the server's own tool schema.
Why sandbox_templates_delete is rated Critical
The tool performs a delete operation on sandbox templates, which is irreversible and destroys data. This fits the Destructive category (irreversibly deletes or overwrites data). Severity is high because deletion of sandbox templates could disrupt development/testing workflows and cannot be undone. Context from sibling tools (account_delete, audit_events_archives_prune) reinforces this is a data-destructive server.
From the tool's definition Tool name contains 'delete' and description states 'sandbox-templates.delete' operation. The verb 'delete' indicates irreversible removal of sandbox template data.
Attacks that exploit this kind of access
The rule that runs sandbox_templates_delete 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_templates_delete, this is the rule to start with:
sandbox_templates_delete 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 sandbox_templates_delete call is checked against it from then on.
Questions about sandbox_templates_delete
Run sandbox-templates.delete 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.
sandbox_templates_delete accepts 1 parameter: templateId. Required: templateId. 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_templates_delete: 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_templates_delete 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 sandbox_templates_delete 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_templates_delete. 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_templates_delete 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