breakpoint_doctor
Check this Breakpoint MCP setup end to end: the Godot binary, the editor addon's install and enable state, the capability groups in force, and the editor/runtime/LSP/DAP bridges. Returns a per-check status with a hint for anything wrong. Read-only — run it first when an editor_*, runtime_*, gd_* ...
This record as markdown: /tools/breakpoint-mcp/breakpoint-doctor.md
What breakpoint_doctor does on Breakpoint
AI agents invoke breakpoint_doctor to trigger actions in Breakpoint. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
live_level | string | — | Which bridges this report insists on: none (default), editor (the three the editor brings up), runtime (the one the running game brings up), all. Takes preceden |
timeout_ms | integer | — | Per-bridge connect timeout (default 1500) |
require_live | boolean | — | Treat an unreachable bridge as a failure rather than information (default false). True means the EDITOR's three bridges — editor, GDScript LSP, GDScript DAP. Th |
include_csharp | boolean | — | Also probe OmniSharp / netcoredbg on PATH (the C# planes) |
Parameters from the server's own tool schema.
Why breakpoint_doctor is rated High
breakpoint_doctor triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs breakpoint_doctor safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For breakpoint_doctor, this is the rule to start with:
breakpoint_doctor 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 Breakpoint, apply this rule, and every breakpoint_doctor call is checked against it from then on.
Questions about breakpoint_doctor
Check this Breakpoint MCP setup end to end: the Godot binary, the editor addon's install and enable state, the capability groups in force, and the editor/runtime/LSP/DAP bridges. Returns a per-check status with a hint for anything wrong. Read-only — run it first when an editor_*, runtime_*, gd_* or dbg_* tool fails to connect. It is categorised as a Execute tool in the Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
breakpoint_doctor accepts 4 parameters: live_level, timeout_ms, require_live, include_csharp. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for breakpoint_doctor: 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 Breakpoint. Nothing to install.
breakpoint_doctor 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 breakpoint_doctor 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 breakpoint_doctor. 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.
breakpoint_doctor is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
Across the catalogue