AI agents invoke abap_lint to trigger actions in 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.
Linting involves executing a static analysis tool against code. While it doesn't modify persistent data, it runs an external process/engine whose behavior depends on the code argument supplied. No data is written or destroyed, but code execution/analysis is triggered, placing it in the Execute category.
From the tool's definition 'LINT ABAP CODE: abap_lint(code=' — the tool runs a linting process on provided ABAP code, which executes an analysis/processing operation against input code
Documented attack patterns abuse exactly the kind of access abap_lint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Abap, and nothing reaches the server without passing your rules. This is the rule we recommend for abap_lint:
{
"version": "1",
"default": "deny",
"tools": {
"abap_lint": {
"limits": [
{
"counter": "abap_lint_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}abap_lint 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.
LINT ABAP CODE: abap_lint(code=. It is categorised as a Execute tool in the Abap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Abap MCP server in PolicyLayer and add a rule for abap_lint: 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 Abap. Nothing to install.
abap_lint 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 abap_lint 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 abap_lint. 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.
abap_lint is provided by the Abap MCP server (marianfoo/abap-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 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.
8 Abap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.