adt_pretty_print

THE RISK

High Risk

Why adt_pretty_print needs a policy

This tool executes the ABAP pretty printer, which is an external code formatting operation. Although stateless and read-only in effect (no persistence, no locks), it triggers execution of a formatter tool on provided input. This falls under Execute rather than Read because it involves running an external operation/formatter.

From the tool's definition Tool description states it will "Run the ABAP pretty printer on supplied source code"; the verb "Run" indicates code execution is the core function.

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

POLICY

How to control adt_pretty_print

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_pretty_print:

policy.json

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

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

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.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claude For Abap tools

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

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Claude For Abap → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-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.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about adt_pretty_print

What does the adt_pretty_print tool do? +

Run the ABAP pretty printer on supplied source code (stateless — no object lookup, no lock). 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_pretty_print? +

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

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

Can I rate-limit adt_pretty_print? +

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

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

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