AI agents call debugpy_list_breakpoints to retrieve information from Debugpy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing breakpoint information without modifying, deleting, or executing any code. It is a read-only query operation analogous to listing or fetching data. The low severity reflects that exposing breakpoint metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name is 'debugpy_list_breakpoints' and description states it 'List[s] all registered breakpoints for this session' — a pure query operation with no side effects or modifications.
Attacks that exploit this kind of access
List all registered breakpoints for this session. It is categorised as a Read tool in the Debugpy MCP Server, which means it retrieves data without modifying state.
Register the Debugpy MCP server in PolicyLayer and add a rule for debugpy_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 Debugpy. Nothing to install.
debugpy_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 debugpy_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 debugpy_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.
debugpy_list_breakpoints is provided by the Debugpy MCP server (will-garrett/debugpy-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 →