Search for RFC functions using keywords in names and descriptions
AI agents call search_rfc_functions to retrieve information from SAP RFC MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries metadata about available RFC functions—it searches and lists available functions without calling them, modifying data, or triggering external operations. The search operation is a read-only retrieval of information about SAP RFC function catalogs. No side effects or state changes occur from searching.
From the tool's definition Tool name 'search_rfc_functions' and description 'Search for RFC functions using keywords in names and descriptions' indicate a query/search operation with no modification or execution of functions.
Documented attack patterns abuse exactly the kind of access search_rfc_functions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SAP RFC MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_rfc_functions:
{
"version": "1",
"default": "deny",
"tools": {
"search_rfc_functions": {}
}
} search_rfc_functions 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 for RFC functions using keywords in names and descriptions. It is categorised as a Read tool in the SAP RFC MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SAP RFC MCP Server MCP server in PolicyLayer and add a rule for search_rfc_functions: 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 SAP RFC MCP Server. Nothing to install.
search_rfc_functions 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_rfc_functions 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_rfc_functions. 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_rfc_functions is provided by the SAP RFC MCP Server MCP server (thupalo/sap-rfc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SAP RFC MCP Server, 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.
15 SAP RFC MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.