debug_draw_sphere
Draw a wireframe debug sphere at a point. Renders in editor and play. Ideal for visualizing a physics_overlap radius or an NPC
This record as markdown: /tools/sbox/debug-draw-sphere.md
What debug_draw_sphere does on Sbox
AI agents invoke debug_draw_sphere to trigger actions in Sbox. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why debug_draw_sphere is rated High
This tool triggers a rendering operation in the game engine environment (editor and play mode), which constitutes executing an external operation with visual side effects. It doesn't read, write persistent data, or destroy anything — it renders a debug visualization. Severity is low as it's purely a debug/visualization tool with minimal blast radius.
From the tool's definition Draw a wireframe debug sphere at a point. Renders in editor and play.
Attacks that exploit this kind of access
The rule that runs debug_draw_sphere 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_draw_sphere, this is the rule to start with:
debug_draw_sphere stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every debug_draw_sphere call is checked against it from then on.
Questions about debug_draw_sphere
Draw a wireframe debug sphere at a point. Renders in editor and play. Ideal for visualizing a physics_overlap radius or an NPC. It is categorised as a Execute tool in the Sbox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sbox MCP server in PolicyLayer and add a rule for debug_draw_sphere: 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.
debug_draw_sphere is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the debug_draw_sphere 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 debug_draw_sphere. 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.
debug_draw_sphere 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.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue