AI agents invoke lint_abap 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.
The tool runs a code analysis engine (abaplint) that processes and returns structured findings about ABAP code. While static analysis itself does not modify production data, it executes external logic to evaluate code, making it an Execute category tool rather than a simple Read.
From the tool's definition Tool performs 'static analysis' via abaplint over ABAP/CDS/behavior-definition sources, analyzing code with potential structural side effects on how code is interpreted.
Attacks that exploit this kind of access
Run abaplint static analysis over ABAP, CDS or behavior-definition sources and return structured findings. 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 lint_abap: 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.
lint_abap 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 lint_abap 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 lint_abap. 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.
lint_abap is provided by the Abap MCP server (abap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →