debug_draw_ray
Draw a debug ray (drawn as an arrow) from an origin along a direction for a given length. Renders in editor and play. Ideal for visualizing a raycast result or a facing/normal direction. Accumulates until debug_clear.
This record as markdown: /tools/sbox/debug-draw-ray.md
What debug_draw_ray does on Sbox
AI agents invoke debug_draw_ray 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_ray is rated High
This tool triggers a rendering operation in the game engine (editor and play modes), causing a visual side effect that persists until explicitly cleared. It is not purely reading data; it actively causes the engine to render debug visuals, making it an Execute action. Severity is low as it only draws visual debug information with no data modification or destructive capability.
From the tool's definition 'Draw a debug ray... Renders in editor and play. Accumulates until debug_clear'
Attacks that exploit this kind of access
The rule that runs debug_draw_ray 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_ray, this is the rule to start with:
debug_draw_ray 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_ray call is checked against it from then on.
Questions about debug_draw_ray
Draw a debug ray (drawn as an arrow) from an origin along a direction for a given length. Renders in editor and play. Ideal for visualizing a raycast result or a facing/normal direction. Accumulates until debug_clear. 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_ray: 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_ray 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_ray 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_ray. 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_ray 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