Run an ADT syntax check on an object. Returns the raw <chkrun:reports> XML. Includes only compile in the context of a main program: for type=include, pass
AI agents invoke adt_syntax_check 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 syntax/compile check against a live SAP system, which is an active operation (not just a passive read). While it doesn't modify or delete data, it triggers real processing on the SAP backend. Severity is medium because misuse could cause performance impact on the SAP system or reveal sensitive information about object structure, but it doesn't alter data.
From the tool's definition 'Run an ADT syntax check on an object' — triggers an active compilation/syntax check operation on a live SAP system via ADT
Documented attack patterns abuse exactly the kind of access adt_syntax_check 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_syntax_check:
{
"version": "1",
"default": "deny",
"tools": {
"adt_syntax_check": {
"limits": [
{
"counter": "adt_syntax_check_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} adt_syntax_check 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 an ADT syntax check on an object. Returns the raw <chkrun:reports> XML. Includes only compile in the context of a main program: for type=include, pass. 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_syntax_check: 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_syntax_check 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_syntax_check 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_syntax_check. 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_syntax_check 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.