adt_debug_step · Claude For Abap MCP: Risk & Policy

WHAT IT DOES

What adt_debug_step does on Claude For Abap

AI agents invoke adt_debug_step to trigger actions in Claude For Abap. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why adt_debug_step needs a policy

This tool drives a live debugger session on a SAP system, stepping through or advancing execution of running ABAP code. It falls under Execute because it actively controls program execution flow in a live system. Misuse could alter program state, skip validations, or cause unintended side effects in production SAP processes.

From the tool's definition 'Advance the attached debuggee (Phase 2, flow control)' — controls execution flow of a running SAP/ABAP debug session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

adt_debug_step Rate-limited

adt_debug_step stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adt_debug_step": {
      "limits": [
        {
          "counter": "adt_debug_step_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude For Abap, so you can run agents against it safely.

FAQ

Questions about adt_debug_step

What does the adt_debug_step tool do? +

Advance the attached debuggee (Phase 2, flow control). It is categorised as a Execute tool in the Claude For Abap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on adt_debug_step? +

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

adt_debug_step is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit adt_debug_step? +

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

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

adt_debug_step 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_step 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 →