Low Risk

get_table_structure

Get the structure/metadata of an SAP table using DDIF_FIELDINFO_GET

How to control get_table_structure ↓

What get_table_structure does on SAP RFC MCP Server

AI agents call get_table_structure 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_table_structure needs a policy

This tool retrieves table structure and metadata information from SAP. It performs no writes, deletes, or executions—only reads data definitions. The function DDIF_FIELDINFO_GET is a read-only metadata lookup utility. Even if an agent misuses it, the worst outcome is information disclosure about table schemas, which has minimal blast radius.

From the tool's definition Tool name 'get_table_structure' and description 'Get the structure/metadata of an SAP table' indicate retrieval of metadata without modification. Uses DDIF_FIELDINFO_GET, which is a standard SAP function for querying table definitions.

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

How to control get_table_structure

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

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

get_table_structure 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_table_structure

What does the get_table_structure tool do? +

Get the structure/metadata of an SAP table using DDIF_FIELDINFO_GET. 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_table_structure? +

Register the SAP RFC MCP Server MCP server in PolicyLayer and add a rule for get_table_structure: 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_table_structure? +

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

Can I rate-limit get_table_structure? +

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

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

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