dbg_set_breakpoints

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/dbg-set-breakpoints.md

WHAT IT DOES

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
`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)

Parameters from the server's own tool schema.

RISK

Why dbg_set_breakpoints is rated Medium

This tool writes/modifies debugging configuration by setting (replacing) breakpoints in a source file. It creates or updates breakpoint data reversibly — breakpoints can be added or removed without permanent damage. No code is executed, no data is deleted, and no financial operations occur. Severity is medium because misuse could interfere with a running debug session or cause unexpected halts in execution.

From the tool's definition Set (replace) the breakpoints for a source file. Applied immediately if a session is running, else buffered until launch.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dbg_set_breakpoints": {
      "limits": [
        {
          "counter": "dbg_set_breakpoints_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 Breakpoint, apply this rule, and every dbg_set_breakpoints call is checked against it from then on.

FAQ

Questions about dbg_set_breakpoints

What does the dbg_set_breakpoints tool do? +

Set (replace) the breakpoints for a source file. Applied immediately if a session is running, else buffered until launch. Feature-detected: the per-line conditions / hit_conditions / log_messages modifiers are only sent when the connected adapter advertises support (supportsConditionalBreakpoints / supportsHitConditionalBreakpoints / supportsLogPoints). On an adapter that advertises them unsupported (e.g. Godot 4.3, which ignores them and would otherwise halt unconditionally) the modifier is dropped and the result includes unsupported_modifiers plus a warning. Detection needs a live session, so set modifiers after dbg_launch. 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.

What parameters does dbg_set_breakpoints accept? +

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.

How do I enforce a policy on dbg_set_breakpoints? +

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.

What risk level is dbg_set_breakpoints? +

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

Can I rate-limit dbg_set_breakpoints? +

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.

How do I block dbg_set_breakpoints completely? +

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.

What MCP server provides dbg_set_breakpoints? +

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.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

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