debug_draw_line

SERVERSbox SOURCEsbox-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sbox/debug-draw-line.md

WHAT IT DOES

What debug_draw_line does on Sbox

AI agents use debug_draw_line to create or update resources in Sbox, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sbox environment.

RISK

Why debug_draw_line is rated Medium

An AI agent can call debug_draw_line faster than any human can review: one bad instruction and it creates or modifies resources in Sbox by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs debug_draw_line 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_line, this is the rule to start with:

debug_draw_line Rate-limited

debug_draw_line stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "debug_draw_line": {
      "limits": [
        {
          "counter": "debug_draw_line_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about debug_draw_line

What does the debug_draw_line tool do? +

Draw a debug line between two world points. Renders in the editor viewport (Gizmo) AND in play mode (DebugOverlay), accumulating until debug_clear. NB: edit-mode gizmos show in the live editor but NOT in take_screenshot/screenshot_from — use capture_view in play mode to see debug draws through the bridge. It is categorised as a Write tool in the Sbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on debug_draw_line? +

Register the Sbox MCP server in PolicyLayer and add a rule for debug_draw_line: 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_draw_line? +

debug_draw_line is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit debug_draw_line? +

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

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

debug_draw_line 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →