AI agents call fetch to retrieve information from Abap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns document content based on an identifier. It is a read-only operation with no side effects, aligning with the Read category. Severity is low because document retrieval typically has minimal blast radius unless the documents contain highly sensitive data, but that context is not evident from the description provided.
From the tool's definition Tool name 'fetch' combined with description 'GET FULL DOCUMENT CONTENT' and the parameter pattern 'id=' indicates retrieval of existing document data. No modification, execution, deletion, or financial operations are implied.
Documented attack patterns abuse exactly the kind of access fetch 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 fetch:
{
"version": "1",
"default": "deny",
"tools": {
"fetch": {}
}
}fetch 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.
GET FULL DOCUMENT CONTENT: fetch(id=. It is categorised as a Read tool in the Abap MCP Server, which means it retrieves data without modifying state.
Register the Abap MCP server in PolicyLayer and add a rule for fetch: 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.
fetch 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 fetch 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 fetch. 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.
fetch 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.