Remove a hardware breakpoint
AI agents call remove_hardware_breakpoint to permanently remove resources in MCP Debug Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a hardware breakpoint is an irreversible action that permanently deletes a debugging control point. While it doesn't destroy user data, it irrecoverably removes a debugging artifact that was set intentionally. This cannot be undone without manually re-adding the breakpoint, and misuse could cause a debugging session to miss critical execution points or allow unintended code execution to proceed unchecked.
From the tool's definition Remove a hardware breakpoint
Attacks that exploit this kind of access
Remove a hardware breakpoint. It is categorised as a Destructive tool in the MCP Debug Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Debug Server MCP server in PolicyLayer and add a rule for remove_hardware_breakpoint: 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.
remove_hardware_breakpoint is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_hardware_breakpoint 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 remove_hardware_breakpoint. 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.
remove_hardware_breakpoint 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 →