adt_delete_object

THE RISK

Critical Risk

Why adt_delete_object needs a policy

This tool permanently removes ABAP objects from a SAP system without possibility of recovery (unless backups exist outside the tool's scope). Deletion is irreversible and constitutes destructive action. In a critical enterprise system like SAP, unauthorized deletion of production code objects could halt business operations, corrupt systems, or cause data loss.

From the tool's definition Tool description states 'Delete an ABAP object' and 'issues DELETE'. The verb 'delete' combined with the mechanism of issuing a DELETE operation indicates irreversible removal of data.

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

POLICY

How to control adt_delete_object

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "adt_delete_object"
  ]
}

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

Create a free account and register Claude For Abap — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claude For Abap tools

Execute adt_pretty_print Run the ABAP pretty printer on supplied source code (stateless — no object lookup, no lock Execute adt_run_atc Run ABAP Test Cockpit (ATC) on one or more objects. ATC endpoint shape varies across NetWe Execute adt_run_atc_package Run ABAP Test Cockpit (ATC) over an ENTIRE package via the full ADT worklist flow (create Execute adt_run_atc_transport Run ABAP Test Cockpit (ATC) over every object in a transport request via the full ADT work Execute adt_run_unit_tests Run ABAP Unit tests for one or more objects (typically test container classes). Execute adt_release_transport Release a transport request. Subject to read-only mode. Execute adt_request Generic ADT REST call — escape hatch for endpoints not covered by a high-level tool. Handl Execute adt_syntax_check Run an ADT syntax check on an object. Returns the raw <chkrun:reports> XML. Includes only

All 45 Claude For Abap tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Claude For Abap → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about adt_delete_object

What does the adt_delete_object tool do? +

Delete an ABAP object. Acquires a lock and issues DELETE. Refused under read-only mode. 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_delete_object? +

Register the Claude For Abap MCP server in PolicyLayer and add a rule for adt_delete_object: 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_delete_object? +

adt_delete_object 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_delete_object? +

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

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

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

Enforce policy on every Claude For Abap tool call.

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

CHECK YOUR STACK →