debug_clear

Remove all debug-draw primitives by destroying the debug holder for the current scene (edit or play). Call before redrawing a fresh frame of debug shapes.

SERVERSbox SOURCEsbox-mcp-server

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/sbox/debug-clear.md

WHAT IT DOES

What debug_clear does on Sbox

AI agents call debug_clear to permanently remove resources in Sbox, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why debug_clear is rated Critical

The tool destroys the debug holder object for the current scene, which is an irreversible removal action. While it only affects debug-draw primitives (not core game data), 'destroying' the holder is a destructive operation that cannot be undone without redrawing all shapes manually.

From the tool's definition Remove all debug-draw primitives by destroying the debug holder

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs debug_clear safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For debug_clear, this is the rule to start with:

debug_clear Hidden

debug_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "debug_clear"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every debug_clear call is checked against it from then on.

FAQ

Questions about debug_clear

What does the debug_clear tool do? +

Remove all debug-draw primitives by destroying the debug holder for the current scene (edit or play). Call before redrawing a fresh frame of debug shapes. It is categorised as a Destructive tool in the Sbox 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 debug_clear? +

Register the Sbox MCP server in PolicyLayer and add a rule for debug_clear: 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 Sbox. Nothing to install.

What risk level is debug_clear? +

debug_clear 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 debug_clear? +

Yes. Add a rate_limit block to the debug_clear 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 debug_clear completely? +

Set action: deny in the PolicyLayer policy for debug_clear. 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 debug_clear? +

debug_clear is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sbox, and thousands of servers like it.

This server

All 207 Sbox tools → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →