Low Risk

list_all_breakpoints

List all breakpoints currently set in the debugger.

How to control list_all_breakpoints ↓

What list_all_breakpoints does on Dap

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

Low Risk

Why list_all_breakpoints needs a policy

This tool queries and returns information about existing breakpoints. It performs no mutations, does not execute code, and does not delete or modify any state. It is purely informational—a read operation with no side effects, making it the least risky category.

From the tool's definition Tool name 'list_all_breakpoints' and description 'List all breakpoints currently set in the debugger' indicate a query operation that retrieves breakpoint data without modifying, executing, or affecting debugger state.

Documented attack patterns abuse exactly the kind of access list_all_breakpoints gives an agent:

How to control list_all_breakpoints

PolicyLayer is an MCP gateway — it sits between your AI agents and Dap, and nothing reaches the server without passing your rules. This is the rule we recommend for list_all_breakpoints:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_all_breakpoints": {}
  }
}

list_all_breakpoints is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Dap — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_all_breakpoints

What does the list_all_breakpoints tool do? +

List all breakpoints currently set in the debugger. It is categorised as a Read tool in the Dap MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_all_breakpoints? +

Register the Dap MCP server in PolicyLayer and add a rule for list_all_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 Dap. Nothing to install.

What risk level is list_all_breakpoints? +

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

Can I rate-limit list_all_breakpoints? +

Yes. Add a rate_limit block to the list_all_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 list_all_breakpoints completely? +

Set action: deny in the PolicyLayer policy for list_all_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 list_all_breakpoints? +

list_all_breakpoints is provided by the Dap MCP server (kashuncheng/dap_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dap tool call.

Start from Dap, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 Dap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.