get_catalog_metadata

ServerSAP Datasphere MCP Server
CategoryRead

WHAT IT DOES

What get_catalog_metadata does on SAP Datasphere MCP Server

AI agents call get_catalog_metadata to retrieve information from SAP Datasphere MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why get_catalog_metadata needs a policy

get_catalog_metadata performs schema discovery and metadata inspection only. It does not create, modify, delete, or execute any operations - it simply returns structural information about available entities, properties, and relationships in OData format. This is a classic Read operation with minimal blast radius even if misused, as it cannot alter data or trigger external actions.

From the tool's definition Tool retrieves and describes metadata structures via 'Get CSDL metadata' and 'OData metadata document' - read-only introspection operations with no modification, deletion, or execution capabilities.

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

POLICY

How to control get_catalog_metadata

PolicyLayer is an MCP gateway — it sits between your AI agents and SAP Datasphere MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_catalog_metadata:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_catalog_metadata": {}
  }
}

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

Create a free account and register SAP Datasphere MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More SAP Datasphere MCP Server tools

Execute execute_query Execute a SQL query against Datasphere data (simulated) Execute query_analytical_data Execute OData queries on analytical models to retrieve aggregated data with dimensions and Execute query_relational_entity Execute OData queries on relational entities for ETL data extraction. Supports large batch Read get_analytical_metadata Retrieve CSDL metadata for analytical consumption of a specific asset. Returns analytical Read get_analytical_model Get the OData service document and metadata for a specific analytical model. Returns entit Read get_analytical_service_document Get the OData service document for a specific analytical asset. Returns the service root w Read get_asset_variables Retrieve input parameters/variables and filter-capability annotations declared in the ODat Read get_available_scopes List available OAuth2 scopes for the current user, showing which scopes are granted and wh

All 31 SAP Datasphere MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_catalog_metadata

What does the get_catalog_metadata tool do? +

Get CSDL metadata for the SAP Datasphere catalog service. Retrieves the OData metadata document (CSDL XML) that describes the catalog service schema including entity types, properties, relationships, and available operations. Essential for understanding the catalog structure. It is categorised as a Read tool in the SAP Datasphere MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_catalog_metadata? +

Register the SAP Datasphere MCP Server MCP server in PolicyLayer and add a rule for get_catalog_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 Datasphere MCP Server. Nothing to install.

What risk level is get_catalog_metadata? +

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

Can I rate-limit get_catalog_metadata? +

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

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

get_catalog_metadata is provided by the SAP Datasphere MCP Server MCP server (mariodefelipe/sap-datasphere-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SAP Datasphere MCP Server tool call.

Start from SAP Datasphere MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

31 SAP Datasphere MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.