dbg_data_breakpoints
Set (replace) data breakpoints — 'watchpoints' that halt when a variable's value changes (DAP dataBreakpointInfo + setDataBreakpoints). Pass watch as a list of { name, variables_ref?, access_type? }: each name is resolved to a dataId via dataBreakpointInfo, then every resolvable id is armed in on...
This record as markdown: /tools/breakpoint-mcp/dbg-data-breakpoints.md
What dbg_data_breakpoints does on Breakpoint
AI agents invoke dbg_data_breakpoints 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 |
|---|---|---|---|
watch | array | — | Variables to watch; omit or [] to clear all data breakpoints |
Parameters from the server's own tool schema.
Why dbg_data_breakpoints is rated High
This tool configures watchpoints/data breakpoints in an active debug session that cause execution to halt when variables change. It actively interferes with a running process's execution flow, which qualifies as Execute. Misuse could disrupt debugging sessions, cause programs to halt unexpectedly, or interfere with production debug sessions if accessible.
From the tool's definition halt when a variable's value changes (DAP dataBreakpointInfo + setDataBreakpoints) ... arms breakpoints in a running debug session ... Requires a running session
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs dbg_data_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_data_breakpoints, this is the rule to start with:
dbg_data_breakpoints 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 dbg_data_breakpoints call is checked against it from then on.
Questions about dbg_data_breakpoints
Set (replace) data breakpoints — 'watchpoints' that halt when a variable's value changes (DAP dataBreakpointInfo + setDataBreakpoints). Pass watch as a list of { name, variables_ref?, access_type? }: each name is resolved to a dataId via dataBreakpointInfo, then every resolvable id is armed in one setDataBreakpoints call. Call with no watch (or []) to clear all data breakpoints. The result reports the armed breakpoints (each with its resolved data_id and verified flag) and any unresolved variables the adapter cannot watch. Requires a running session; NOT gated (it only configures the debugger). Feature-detected: on an adapter that does not advertise supportsDataBreakpoints it returns a clear "unsupported" message without sending any request. 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.
dbg_data_breakpoints accepts 1 parameter: watch. 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_data_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_data_breakpoints 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 dbg_data_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_data_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_data_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.
Across the catalogue