Critical Risk →

dbg_delete_bp

Delete breakpoints

How to control dbg_delete_bp ↓

What dbg_delete_bp does on Ida Domain

AI agents call dbg_delete_bp to permanently remove resources in Ida Domain — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why dbg_delete_bp needs a policy

Deleting breakpoints is an irreversible modification of debugging state. While the blast radius is limited to the debugging session (not the target binary itself), the action cannot be undone and represents destructive manipulation of reverse engineering artifacts. This ranks above Write (which is reversible) and is more severe than Read or Execute alone.

From the tool's definition Tool name 'dbg_delete_bp' explicitly performs deletion of breakpoints. Description states 'Delete breakpoints' — a destructive operation that cannot be reversed without manual recreation.

Documented attack patterns abuse exactly the kind of access dbg_delete_bp gives an agent:

How to control dbg_delete_bp

PolicyLayer is an MCP gateway — it sits between your AI agents and Ida Domain, and nothing reaches the server without passing your rules. This is the rule we recommend for dbg_delete_bp:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "dbg_delete_bp"
  ]
}

dbg_delete_bp disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Ida Domain — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about dbg_delete_bp

What does the dbg_delete_bp tool do? +

Delete breakpoints. It is categorised as a Destructive tool in the Ida Domain 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 dbg_delete_bp? +

Register the Ida Domain MCP server in PolicyLayer and add a rule for dbg_delete_bp: 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 Ida Domain. Nothing to install.

What risk level is dbg_delete_bp? +

dbg_delete_bp 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 dbg_delete_bp? +

Yes. Add a rate_limit block to the dbg_delete_bp 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 dbg_delete_bp completely? +

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

dbg_delete_bp is provided by the Ida Domain MCP server (xxyyue/ida_domain_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ida Domain tool call.

Start from Ida Domain, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

74 Ida Domain tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.