This record as markdown: /tools/yanhuifair-godot-mcp/editor-debug-break.md
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 editor_debug_break is rated High
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
The rule that runs editor_debug_break safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For editor_debug_break, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every editor_debug_break call is checked against it from then on.
Questions about editor_debug_break
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.
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.
editor_debug_break 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 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.
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.
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.
More on Godot, and thousands of servers like it.
Across the catalogue