Low Risk

get_function_metadata

Get comprehensive metadata for an RFC function including parameters, types, and descriptions

How to control get_function_metadata ↓

What get_function_metadata does on SAP RFC MCP Server

AI agents call get_function_metadata 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.

Low Risk

Why get_function_metadata needs a policy

This tool queries and retrieves metadata about RFC functions without creating, modifying, deleting, or executing any operations. It is purely informational in nature, making it a Read category tool. Severity is low because metadata retrieval poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name is 'get_function_metadata' and description states it retrieves 'comprehensive metadata for an RFC function including parameters, types, and descriptions'.

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

How to control get_function_metadata

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_function_metadata": {}
  }
}

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

  1. Create a free account and register SAP RFC MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_function_metadata

What does the get_function_metadata tool do? +

Get comprehensive metadata for an RFC function including parameters, types, 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.

How do I enforce a policy on get_function_metadata? +

Register the SAP RFC MCP Server MCP server in PolicyLayer and add a rule for get_function_metadata: 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.

What risk level is get_function_metadata? +

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

Can I rate-limit get_function_metadata? +

Yes. Add a rate_limit block to the get_function_metadata 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 get_function_metadata completely? +

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

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

Enforce policy on every SAP RFC MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.