List all active hardware breakpoints with hit counts and status
AI agents call list_hardware_breakpoints to retrieve information from MCP Debug Server 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 information about existing hardware breakpoints without modifying, creating, or deleting them. It is purely informational, making it a Read category tool. Within a debugging context where an agent has already attached to a process, listing breakpoint state poses minimal risk (low severity) as it merely queries existing debugger state.
From the tool's definition Tool name is 'list_hardware_breakpoints' and description states it 'List all active hardware breakpoints with hit counts and status'. The verb 'list' and the read-only nature of querying breakpoint metadata indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all active hardware breakpoints with hit counts and status. It is categorised as a Read tool in the MCP Debug Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Debug Server MCP server in PolicyLayer and add a rule for list_hardware_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 Debug Server. Nothing to install.
list_hardware_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_hardware_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_hardware_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_hardware_breakpoints is provided by the MCP Debug Server MCP server (nickzer0/mcp-debugserver). 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 →