adt_debug_delete_watchpoint

Delete a watchpoint by id (from adt_debug_set_watchpoint). Phase 3, WRITE — refused under read-only mode. Best-effort until validated live.

Server Claude For Abap yzonur/claude-for-abap
Category Destructive
Risk class Critical
Parameters 00 required

What adt_debug_delete_watchpoint does on Claude For Abap

AI agents call adt_debug_delete_watchpoint 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.

Why adt_debug_delete_watchpoint needs a policy

Deleting a watchpoint is a destructive, non-reversible action (the watchpoint is removed). While the blast radius is limited to a debug session artifact rather than business data, deletion operations are classified as Destructive per the severity hierarchy. Severity is medium because watchpoints are ephemeral debug constructs with limited broader impact if accidentally deleted.

From the tool's definition 'Delete a watchpoint by id' — the action is irreversible deletion of a debug watchpoint; 'WRITE — refused under read-only mode' confirms it mutates state.

Questions about adt_debug_delete_watchpoint

What does the adt_debug_delete_watchpoint tool do? +

Delete a watchpoint by id (from adt_debug_set_watchpoint). Phase 3, WRITE — refused under read-only mode. Best-effort until validated live. 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.

How do I enforce a policy on adt_debug_delete_watchpoint? +

Register the Claude For Abap MCP server in PolicyLayer and add a rule for adt_debug_delete_watchpoint: 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.

What risk level is adt_debug_delete_watchpoint? +

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

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

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

adt_debug_delete_watchpoint 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.

// THE FULL RECORD

adt_debug_delete_watchpoint 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.