sandbox_files_remove
Run sandbox-files.remove through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/sandbox-files-remove.md
What sandbox_files_remove does on Appaloft
AI agents call sandbox_files_remove 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 |
|---|---|---|---|
path | string | Yes | |
recursive | boolean | — | |
sandboxId | string | Yes |
Parameters from the server's own tool schema.
Why sandbox_files_remove is rated Critical
File removal is a destructive operation that cannot be undone. While the scope is limited to 'sandbox' files (suggesting some containment), deletion of any files represents a high-severity irreversible action. Destructive operations take precedence over Execute category per classification rules.
From the tool's definition Tool name is 'sandbox_files_remove' which explicitly performs file removal/deletion. Description states it 'Run[s] sandbox-files.remove' — the verb 'remove' indicates irreversible deletion of files.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs sandbox_files_remove 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_files_remove, this is the rule to start with:
sandbox_files_remove 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_files_remove call is checked against it from then on.
Questions about sandbox_files_remove
Run sandbox-files.remove 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_files_remove accepts 3 parameters: path, recursive, sandboxId. Required: path, 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_files_remove: 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_files_remove 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_files_remove 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_files_remove. 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_files_remove 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