Lists all breakpoints set in a debugging session, including their locations and conditions.
AI agents call list_breakpoints to retrieve information from MCP JS Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of debug session state. Listing breakpoints has no side effects and cannot modify application state, data, or code execution. The information retrieved is debug metadata that does not affect the debugged application's behavior.
From the tool's definition Tool 'list_breakpoints' retrieves and queries breakpoint information from a debugging session without modifying or executing code. The description states it 'Lists all breakpoints' with no mention of creating, modifying, or deleting breakpoints.
Attacks that exploit this kind of access
Lists all breakpoints set in a debugging session, including their locations and conditions. It is categorised as a Read tool in the MCP JS Debugger MCP Server, which means it retrieves data without modifying state.
Register the MCP JS Debugger 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 MCP JS Debugger. Nothing to install.
list_breakpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
list_breakpoints is provided by the MCP JS Debugger MCP server (johngrimes/mcp-js-debugger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →