New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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...

SERVERBreakpoint SOURCEbreakpoint-mcp
Low RISK CLASS
Category Read
Parameters 10 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What dbg_data_breakpoints does on Breakpoint

AI agents call dbg_data_breakpoints to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
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 Low

Even though dbg_data_breakpoints only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsBulk/mass operation — affects multiple targets

Questions about dbg_data_breakpoints

What does the dbg_data_breakpoints tool do? +

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. 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. Measured: no Godot build this project tests advertises it — 4.3-stable and 4.7-stable both refuse this tool, so on a shipped engine it is unsupported surface today rather than a feature you can reach; see docs/dap_capability_ledger.json. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.

What parameters does dbg_data_breakpoints accept? +

dbg_data_breakpoints accepts 1 parameter: watch. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dbg_data_breakpoints? +

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.

What risk level is dbg_data_breakpoints? +

dbg_data_breakpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dbg_data_breakpoints? +

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.

How do I block dbg_data_breakpoints completely? +

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.

What MCP server provides dbg_data_breakpoints? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Breakpoint's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.