New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_sandbox_policy

Delete a sandbox policy. Fails if any active sessions are using it.

SERVERNodebench SOURCEnodebench-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_sandbox_policy

What does the delete_sandbox_policy tool do? +

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.

How do I enforce a policy on delete_sandbox_policy? +

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.

What risk level is delete_sandbox_policy? +

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.

Can I rate-limit delete_sandbox_policy? +

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.

How do I block delete_sandbox_policy completely? +

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.

What MCP server provides delete_sandbox_policy? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nodebench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.