[LEVEL 2 - METADATA] Get complete schema details for a specific entity. Returns ALL properties with types, keys, nullable flags, maxLength, and capabilities (creatable, updatable, deletable). Use this after discover-sap-data to get full details needed for execute-sap-operation. Uses technical use...
AI agents call get-entity-metadata to retrieve information from SAP OData to MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves schema metadata from SAP systems. It has no side effects—it does not create, modify, delete, or execute operations on business entities. While it provides structural information about what operations are possible (creatable, updatable, deletable flags), the tool itself only reads and returns metadata.
From the tool's definition Tool description explicitly states 'Get complete schema details' and 'Returns ALL properties with types, keys, nullable flags, maxLength, and capabilities.' The word 'Get' combined with returning metadata about entities indicates a read-only operation that…
Documented attack patterns abuse exactly the kind of access get-entity-metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SAP OData to MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-entity-metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get-entity-metadata": {}
}
}get-entity-metadata 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.
[LEVEL 2 - METADATA] Get complete schema details for a specific entity. Returns ALL properties with types, keys, nullable flags, maxLength, and capabilities (creatable, updatable, deletable). Use this after discover-sap-data to get full details needed for execute-sap-operation. Uses technical user (no auth needed). It is categorised as a Read tool in the SAP OData to MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SAP OData to MCP Server MCP server in PolicyLayer and add a rule for get-entity-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 OData to MCP Server. Nothing to install.
get-entity-metadata 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 get-entity-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.
Set action: deny in the PolicyLayer policy for get-entity-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.
get-entity-metadata is provided by the SAP OData to MCP Server MCP server (lemaiwo/btp-sap-odata-to-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SAP OData to 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.
3 SAP OData to MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.