delete_sandbox_policy
Delete a sandbox policy. Fails if any active sessions are using it.
This record as markdown: /tools/io-github-homenshum-nodebench/delete-sandbox-policy.md
What delete_sandbox_policy does on Nodebench
AI agents call delete_sandbox_policy to permanently remove resources in Nodebench, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_sandbox_policy is rated Critical
This tool permanently removes a sandbox policy configuration. While deletion may fail if in use (preventing accidental destruction), the core function is irreversible data removal. The blast radius is significant for system security and operations—deleting an active or recently-used policy could disrupt session management or leave systems in an inconsistent state.
From the tool's definition delete_sandbox_policy: 'Delete a sandbox policy'. The verb 'Delete' indicates irreversible removal of data/configuration. The qualifier 'Fails if any active sessions are using it' confirms the action targets existing resources.
Attacks that exploit this kind of access
The rule that runs delete_sandbox_policy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_sandbox_policy, this is the rule to start with:
delete_sandbox_policy 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 Nodebench, apply this rule, and every delete_sandbox_policy call is checked against it from then on.
Questions about delete_sandbox_policy
Delete a sandbox policy. Fails if any active sessions are using it. It is categorised as a Destructive tool in the Nodebench MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nodebench MCP server in PolicyLayer and add a rule for delete_sandbox_policy: 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 Nodebench. Nothing to install.
delete_sandbox_policy 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 delete_sandbox_policy 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 delete_sandbox_policy. 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.
delete_sandbox_policy is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
Across the catalogue