editor_debug_break · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_debug_break does on Godot

AI agents invoke editor_debug_break to trigger actions in Godot. 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 IT NEEDS A POLICY

Why editor_debug_break needs a policy

This tool triggers a debugger break, interrupting the execution of a running Godot program. It is an external operation that affects the execution state of the engine/game process. It doesn't delete data (not Destructive) or move money (not Financial), but it does trigger an external operation that halts execution flow, placing it in the Execute category.

From the tool's definition Stop execution (break) in debugger

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_debug_break Rate-limited

editor_debug_break 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_debug_break": {
      "limits": [
        {
          "counter": "editor_debug_break_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot, so you can run agents against it safely.

FAQ

Questions about editor_debug_break

What does the editor_debug_break tool do? +

Stop execution (break) in debugger. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on editor_debug_break? +

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

What risk level is editor_debug_break? +

editor_debug_break is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit editor_debug_break? +

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

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

editor_debug_break is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

editor_debug_break is one line of Godot's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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