list_breakpoints

THE RISK

Low Risk

Why list_breakpoints needs a policy

This tool retrieves and displays existing breakpoint data without modifying, executing, or deleting anything. It is purely informational, similar to a 'list' or 'get' operation. While it provides debugging state information, it cannot be misused to cause harm to code execution or data.

From the tool's definition Tool name 'list_breakpoints' and description 'View all currently set breakpoints' indicate a query/retrieval operation with no side effects.

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control list_breakpoints

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_breakpoints": {}
  }
}

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

Create a free account and register DebugMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More DebugMCP tools

Destructive clear_all_breakpoints Clear all breakpoints at once. Use this after verifying the root cause to clean up before Destructive remove_breakpoint Remove a breakpoint that is no longer needed. Execute continue_execution Resume program execution until the next breakpoint is hit or the program completes. Execute evaluate_expression Powerful runtime expression evaluator: Test hypotheses, check computed values, call method Execute restart_debugging Restart the debug session from the beginning with the same configuration. Execute start_debugging Start a VS Code debug session for a source file, optionally for a single test method. Execute step_into Dive into the current line of code. Execute step_out Step out of the current function

All 13 DebugMCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_breakpoints

What does the list_breakpoints tool do? +

View all currently set breakpoints across all files. It is categorised as a Read tool in the DebugMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_breakpoints? +

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

What risk level is list_breakpoints? +

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

Can I rate-limit list_breakpoints? +

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

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

list_breakpoints is provided by the Debug MCP server (microsoft/debugmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DebugMCP tool call.

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

CHECK YOUR STACK →