Set breakpoints and logpoints in a source file (DAP standard). Tips: (1) when using logMessage with {expr}, place the logpoint at the next executable statement after the variables used in {expr} are assigned/updated; (2) conditions are evaluated at the breakpoint line as well — place the breakpoi...
AI agents use setBreakpoints to create or update resources in MCP Chrome Debugger Protocol — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Chrome Debugger Protocol environment.
This tool modifies the debugging state of a running process by setting breakpoints and logpoints in source files. It creates/modifies debug configurations rather than reading data, executing code, or destroying anything. Misuse could cause a process to halt unexpectedly at injected breakpoints, but effects are reversible (breakpoints can be cleared), placing it in Write category with medium severity.
From the tool's definition Set breakpoints and logpoints in a source file (DAP standard)
Attacks that exploit this kind of access
Set breakpoints and logpoints in a source file (DAP standard). Tips: (1) when using logMessage with {expr}, place the logpoint at the next executable statement after the variables used in {expr} are assigned/updated; (2) conditions are evaluated at the breakpoint line as well — place the breakpoint after variables referenced in condition are assigned/updated. It is categorised as a Write tool in the MCP Chrome Debugger Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Chrome Debugger Protocol MCP server in PolicyLayer and add a rule for setBreakpoints: 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.
setBreakpoints is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setBreakpoints 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 setBreakpoints. 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.
setBreakpoints 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 →