AI agents call GetInterface to retrieve information from MCP ABAP ADT without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves interface definitions from a SAP ABAP system, which is purely informational. It does not modify, delete, execute, or trigger any side effects. Consistent with sibling tools (GetClass, GetFunction, GetProgram, etc.), it falls squarely into the Read category.
From the tool's definition Retrieve ABAP interface source code — a read-only operation that queries and returns existing source code without modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access GetInterface gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP ABAP ADT, and nothing reaches the server without passing your rules. This is the rule we recommend for GetInterface:
{
"version": "1",
"default": "deny",
"tools": {
"GetInterface": {}
}
} GetInterface is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve ABAP interface source code. It is categorised as a Read tool in the MCP ABAP ADT MCP Server, which means it retrieves data without modifying state.
Register the MCP ABAP ADT MCP server in PolicyLayer and add a rule for GetInterface: 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 MCP ABAP ADT. Nothing to install.
GetInterface is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the GetInterface 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 GetInterface. 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.
GetInterface is provided by the MCP ABAP ADT MCP server (mario-andreschak/mcp-abap-adt). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP ABAP ADT, 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.
13 MCP ABAP ADT tools catalogued and risk-classified — across an index of 43,000+ MCP servers.