dbg_set_breakpoints
Set (replace) the breakpoints for a source file: applied now if a session is running, else buffered until launch. Refuses a source that can never bind: a missing file, a directory, an empty path (the project root), or a path outside the Godot project root, absolute ones included (unlike cs_dbg_se...
This record as markdown: /tools/breakpoint-mcp/dbg-set-breakpoints.md
What dbg_set_breakpoints does on Breakpoint
AI agents use dbg_set_breakpoints to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Script path (res://..., absolute, or project-relative) |
lines | array | Yes | 1-based line numbers |
conditions | array | — | Optional per-line condition expressions (aligned to lines, use null to skip a line); break only when the expression is true. Gated on supportsConditionalBreakpo |
log_messages | array | — | Optional per-line log messages aligned to lines; a message turns that breakpoint into a LOGPOINT (logs and continues, never halts). {expr} interpolates (null to |
hit_conditions | array | — | Optional per-line hit expressions aligned to lines, e.g. '>3' or '%5' — break based on hit count (null to skip). Gated on supportsHitConditionalBreakpoints — Me |
Parameters from the server's own tool schema.
Why dbg_set_breakpoints is rated Medium
An AI agent can call dbg_set_breakpoints faster than any human can review: one bad instruction and it creates or modifies resources in Breakpoint by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (path) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs dbg_set_breakpoints 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 dbg_set_breakpoints, this is the rule to start with:
dbg_set_breakpoints 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every dbg_set_breakpoints call is checked against it from then on.
Questions about dbg_set_breakpoints
Set (replace) the breakpoints for a source file: applied now if a session is running, else buffered until launch. Refuses a source that can never bind: a missing file, a directory, an empty path (the project root), or a path outside the Godot project root, absolute ones included (unlike cs_dbg_set_breakpoints), since Godot binds breakpoints only to scripts in the project it runs. The per-line conditions / hit_conditions / log_messages modifiers are sent only when the adapter advertises supportsConditionalBreakpoints / supportsHitConditionalBreakpoints / supportsLogPoints. Measured: no Godot build this project tests advertises it; 4.3-stable and 4.7-stable advertise none of the three and IGNORE the modifiers, so such a breakpoint would halt unconditionally (docs/dap_capability_ledger.json). They are dropped and reported as unsupported_modifiers plus a warning; set before a session exists, the result says modifier_detection: "deferred" and dbg_launch reports what the handshake actually dropped. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
dbg_set_breakpoints accepts 5 parameters: path, lines, conditions, log_messages, hit_conditions. Required: path, lines. 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 dbg_set_breakpoints: 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.
dbg_set_breakpoints is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dbg_set_breakpoints 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 dbg_set_breakpoints. 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.
dbg_set_breakpoints 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.
This server
Across the catalogue