Get all breakpoints organized by file, including conditions, hit counts, and log messages.
AI agents call debug_get_breakpoints to retrieve information from Polybugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves debugging metadata about breakpoints that have been set in a debugger session. It performs no state changes, execution of code, deletion, or financial operations. It is purely informational—returning structured data about the current debugging configuration.
From the tool's definition Tool name 'debug_get_breakpoints' and description 'Get all breakpoints' indicate a query/retrieval operation with no side effects. The description specifies reading existing breakpoint metadata (conditions, hit counts, log messages) without modification.
Attacks that exploit this kind of access
Get all breakpoints organized by file, including conditions, hit counts, and log messages. It is categorised as a Read tool in the Polybugger MCP Server, which means it retrieves data without modifying state.
Register the Polybugger MCP server in PolicyLayer and add a rule for debug_get_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 Polybugger. Nothing to install.
debug_get_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 debug_get_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 debug_get_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.
debug_get_breakpoints is provided by the Polybugger MCP server (wilfoa/polybugger-mcp). 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 →