GetFunction

THE RISK

Low Risk

Why GetFunction needs a policy

This tool retrieves source code artifacts from an SAP ABAP system without side effects. It queries and returns data only. While the retrieved code could theoretically be analyzed for exploits, the tool itself performs no destructive, executable, or financial operations.

From the tool's definition Tool name is 'GetFunction' and description states 'Retrieve ABAP Function Module source code' — a read-only operation with no modification, deletion, or execution of code.

Documented attack patterns abuse exactly the kind of access GetFunction gives an agent:

POLICY

How to control GetFunction

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 GetFunction:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "GetFunction": {}
  }
}

GetFunction is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MCP ABAP ADT — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP ABAP ADT tools

Read GetClass Retrieve ABAP class source code Read GetFunctionGroup Retrieve ABAP Function Group source code Read GetInclude Retrieve ABAP Include Source Code Read GetInterface Retrieve ABAP interface source code Read GetPackage Retrieve ABAP package details Read GetProgram Retrieve ABAP program source code Read GetStructure Retrieve ABAP Structure Read GetTable Retrieve ABAP table structure

All 13 MCP ABAP ADT tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about GetFunction

What does the GetFunction tool do? +

Retrieve ABAP Function Module source code. It is categorised as a Read tool in the MCP ABAP ADT MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on GetFunction? +

Register the MCP ABAP ADT MCP server in PolicyLayer and add a rule for GetFunction: 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.

What risk level is GetFunction? +

GetFunction is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit GetFunction? +

Yes. Add a rate_limit block to the GetFunction 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.

How do I block GetFunction completely? +

Set action: deny in the PolicyLayer policy for GetFunction. 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.

What MCP server provides GetFunction? +

GetFunction 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.

Enforce policy on every MCP ABAP ADT tool call.

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.

CHECK YOUR STACK →