Run ABAP Unit tests for one or more objects (typically test container classes).
AI agents invoke adt_run_unit_tests 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 ABAP Unit tests, which means it runs arbitrary ABAP code in the SAP production or development environment. While unit tests are typically intended to be non-destructive and self-contained, they execute code whose effects depend on what the test code does—it could potentially modify system state, call external services, or have side effects beyond simple assertions.
From the tool's definition Tool name 'adt_run_unit_tests' and description 'Run ABAP Unit tests for one or more objects' explicitly indicates execution of code. Running unit tests triggers arbitrary ABAP code execution within the SAP system.
Documented attack patterns abuse exactly the kind of access adt_run_unit_tests 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_unit_tests:
{
"version": "1",
"default": "deny",
"tools": {
"adt_run_unit_tests": {
"limits": [
{
"counter": "adt_run_unit_tests_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} adt_run_unit_tests 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 Unit tests for one or more objects (typically test container classes). 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_unit_tests: 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_unit_tests 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_unit_tests 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_unit_tests. 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_unit_tests 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.