Get valid breakpoint locations in source file (DAP standard)
AI agents call breakpointLocations to retrieve information from MCP Chrome Debugger Protocol without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and returns information about where breakpoints can be set in a source file. It is a passive inspection operation that does not modify the debugged process, execute arbitrary code, or have side effects. The 'Get' verb and 'locations' object type confirm it is purely retrieving debugging information, making it a Read category tool with low severity.
From the tool's definition Tool name 'breakpointLocations' and description 'Get valid breakpoint locations in source file' indicate a query operation that retrieves debugging metadata without modifying state or executing code.
Attacks that exploit this kind of access
Get valid breakpoint locations in source file (DAP standard). It is categorised as a Read tool in the MCP Chrome Debugger Protocol MCP Server, which means it retrieves data without modifying state.
Register the MCP Chrome Debugger Protocol MCP server in PolicyLayer and add a rule for breakpointLocations: 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 Chrome Debugger Protocol. Nothing to install.
breakpointLocations 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 breakpointLocations 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 breakpointLocations. 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.
breakpointLocations is provided by the MCP Chrome Debugger Protocol MCP server (vitalyostanin/mcp-chrome-debugger-protocol). 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 →