AI agents call search 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 performs a read-only search operation against ABAP/RAP documentation. It retrieves information based on a query parameter but does not create, modify, delete, or execute any operations. Search operations are classified as Read category with low severity since they have no side effects on system state or data persistence.
From the tool's definition Tool description states 'SEARCH ABAP/RAP DOCUMENTATION' with parameter 'query=', indicating a search operation. Sibling tools include 'fetch', 'sap_community_search', and 'sap_discovery_center_search', all of which are clearly data retrieval functions.
Documented attack patterns abuse exactly the kind of access search 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 search:
{
"version": "1",
"default": "deny",
"tools": {
"search": {}
}
}search 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.
SEARCH ABAP/RAP DOCUMENTATION: search(query=. 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 search: 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.
search 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 search 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 search. 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.
search 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.