delete_breakpoint

Delete a breakpoint.

Server WineDbg MCP Server maci0/mcp-winedbg
Category Destructive
Risk class Critical
Parameters 00 required

What delete_breakpoint does on WineDbg MCP Server

AI agents call delete_breakpoint to permanently remove resources in WineDbg MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_breakpoint needs a policy

Deleting a breakpoint is an irreversible action within the debugging session context; once removed, the breakpoint configuration is gone and cannot be recovered. This falls under Destructive as the operation cannot be undone without manually re-creating the breakpoint. Severity is medium since misuse affects only the debugging session, not production data.

From the tool's definition 'delete_breakpoint' - removes a breakpoint irreversibly from the debugging session

Questions about delete_breakpoint

What does the delete_breakpoint tool do? +

Delete a breakpoint. It is categorised as a Destructive tool in the WineDbg MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_breakpoint? +

Register the WineDbg MCP Server MCP server in PolicyLayer and add a rule for delete_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 WineDbg MCP Server. Nothing to install.

What risk level is delete_breakpoint? +

delete_breakpoint is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_breakpoint? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_breakpoint completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_breakpoint? +

delete_breakpoint is provided by the WineDbg MCP Server MCP server (maci0/mcp-winedbg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.