debuggerDeleteListener · ABAP-ADT-API MCP-Server MCP

WHAT IT DOES

What debuggerDeleteListener does on ABAP-ADT-API MCP-Server

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

Parameter	Type	Required	Description
`user`	string	—	The user.
`ideId`	string	—	The IDE ID.
`terminalId`	string	—	The terminal ID.
`debuggingMode`	string	—	The debugging mode.

Parameters from the server's own tool schema.

THE RISK

Critical Risk

Why debuggerDeleteListener needs a policy

The tool name contains 'Delete' and the description states it 'Stops a debug listener', indicating it terminates/removes an active debugging session or listener. This is an irreversible action (you cannot 'un-stop' a listener without restarting it), placing it in the Destructive category. Severity is medium as the blast radius is limited to debug sessions rather than production data.

From the tool's definition debuggerDeleteListener - 'Stops a debug listener' - the word 'Delete' in the tool name and 'Stops' in the description imply termination/removal of a running listener, which is not easily reversible.

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

POLICY

How to control debuggerDeleteListener

PolicyLayer is an MCP gateway — it sits between your AI agents and ABAP-ADT-API MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for debuggerDeleteListener:

policy.json

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

debuggerDeleteListener 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 ABAP-ADT-API MCP-Server — 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 ABAP-ADT-API MCP-Server tools

Destructive debuggerDeleteBreakpoints Deletes breakpoints. Destructive deleteObject Deletes an ABAP object from the system Destructive dropSession Clear local session cache Destructive tracesDelete Deletes a trace. Destructive tracesDeleteConfiguration Deletes a trace configuration. Destructive transportDelete Deletes a transport. Destructive gitUnlinkRepo Unlinks a Git repository. Execute runClass Runs a class.

All 127 ABAP-ADT-API MCP-Server 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 ABAP-ADT-API MCP-Server → 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 debuggerDeleteListener

What does the debuggerDeleteListener tool do? +

Stops a debug listener. It is categorised as a Destructive tool in the ABAP-ADT-API MCP-Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does debuggerDeleteListener accept? +

debuggerDeleteListener accepts 4 parameters: user, ideId, terminalId, debuggingMode. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on debuggerDeleteListener? +

Register the ABAP-ADT-API MCP-Server MCP server in PolicyLayer and add a rule for debuggerDeleteListener: 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 ABAP-ADT-API MCP-Server. Nothing to install.

What risk level is debuggerDeleteListener? +

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

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

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

debuggerDeleteListener is provided by the ABAP-ADT-API MCP-Server MCP server (mario-andreschak/mcp-abap-abap-adt-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ABAP-ADT-API MCP-Server tool call.

Start from ABAP-ADT-API MCP-Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

127 ABAP-ADT-API MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.