Run ABAP Test Cockpit (ATC) over an ENTIRE package via the full ADT worklist flow (create worklist → run → fetch results). Returns parsed findings (check, message, priority, location) plus a priority histogram and the worklist id. When checkVariant is omitted, the system default check variant fro...
AI agents invoke adt_run_atc_package 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.
This tool executes a static code analysis workflow at scale across an entire package, creating artifacts (worklist) and triggering system operations (ATC run). While the analysis itself is non-destructive and returns read-only results (findings, histogram), the act of running ATC creates side effects in the SAP system (worklist creation, analysis execution) and consumes resources.
From the tool's definition Tool 'runs' ABAP Test Cockpit (ATC) 'over an ENTIRE package via the full ADT worklist flow (create worklist → run → fetch results)'.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access adt_run_atc_package gives an agent:
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_run_atc_package:
{
"version": "1",
"default": "deny",
"tools": {
"adt_run_atc_package": {
"limits": [
{
"counter": "adt_run_atc_package_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}adt_run_atc_package 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.
Free to start. No card required.
Run ABAP Test Cockpit (ATC) over an ENTIRE package via the full ADT worklist flow (create worklist → run → fetch results). Returns parsed findings (check, message, priority, location) plus a priority histogram and the worklist id. When checkVariant is omitted, the system default check variant from ATC customizing is used. This is the bulk counterpart to adt_run_atc (single object). 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.
Register the Claude For Abap MCP server in PolicyLayer and add a rule for adt_run_atc_package: 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.
adt_run_atc_package is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adt_run_atc_package 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.
Set action: deny in the PolicyLayer policy for adt_run_atc_package. 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.
adt_run_atc_package 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.
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.
Free to start. No card required.
45 Claude For Abap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.