Browse all repository objects in a SAP Datasphere space including tables, views, analytical models, data flows, and transformations. This tool provides comprehensive metadata, dependency information, and lineage for design-time objects. Use this for object inventory, data cataloging, and understa...
AI agents call list_repository_objects 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.
This is a Read operation that queries and retrieves metadata about repository objects without side effects. However, severity is medium rather than low because: (1) it operates on a production SAP Datasphere system with real tenant data; (2) it exposes comprehensive metadata including dependency information and lineage across multiple object types (tables, views, analytical models, data flows, transformations),…
From the tool's definition Tool description states it 'Browse[s] all repository objects' and 'provides comprehensive metadata, dependency information, and lineage for design-time objects.' The verbs are 'Browse,' 'understanding what assets exist,' and retrieval of metadata—all…
Documented attack patterns abuse exactly the kind of access list_repository_objects gives an agent:
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 list_repository_objects:
{
"version": "1",
"default": "deny",
"tools": {
"list_repository_objects": {}
}
} list_repository_objects 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.
Browse all repository objects in a SAP Datasphere space including tables, views, analytical models, data flows, and transformations. This tool provides comprehensive metadata, dependency information, and lineage for design-time objects. Use this for object inventory, data cataloging, and understanding what assets exist in a space. It is categorised as a Read tool in the SAP Datasphere MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SAP Datasphere MCP Server MCP server in PolicyLayer and add a rule for list_repository_objects: 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.
list_repository_objects 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 list_repository_objects 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 list_repository_objects. 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.
list_repository_objects 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.
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.
Free to start. No card required.
31 SAP Datasphere MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.