Delete an external debugger breakpoint by its id (from adt_debug_set_breakpoint).
AI agents call adt_debug_delete_breakpoint to permanently remove resources in Claude For Abap — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a debugger breakpoint. While the blast radius is low (breakpoints are debugging artifacts with no direct impact on production data or code), the deletion is a destructive operation that cannot be undone without recreating the breakpoint. Severity is low because misuse only affects debugging sessions, not production SAP objects or data.
From the tool's definition Delete an external debugger breakpoint by its id
Attacks that exploit this kind of access
Delete an external debugger breakpoint by its id (from adt_debug_set_breakpoint). It is categorised as a Destructive tool in the Claude For Abap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude For Abap MCP server in PolicyLayer and add a rule for adt_debug_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 Claude For Abap. Nothing to install.
adt_debug_delete_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 adt_debug_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.
Set action: deny in the PolicyLayer policy for adt_debug_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.
adt_debug_delete_breakpoint is provided by the Claude For Abap MCP server (yzonur/claude-for-abap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
adt_debug_delete_breakpoint is one line of Claude For Abap's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →