Global search across all repository objects in SAP Datasphere. Search through tables, views, analytical models, data flows, and transformations. Provides comprehensive object discovery with lineage and dependency information.
AI agents call search_repository 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.
search_repository is fundamentally a Read operation—it retrieves and queries metadata about repository objects (tables, views, models, flows, transformations) and provides information about lineage and dependencies. There are no write, delete, or execution side effects described.
From the tool's definition "Global search across all repository objects in SAP Datasphere. Search through tables, views, analytical models, data flows, and transformations.
Documented attack patterns abuse exactly the kind of access search_repository 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 search_repository:
{
"version": "1",
"default": "deny",
"tools": {
"search_repository": {}
}
} search_repository 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.
Global search across all repository objects in SAP Datasphere. Search through tables, views, analytical models, data flows, and transformations. Provides comprehensive object discovery with lineage and dependency information. 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 search_repository: 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.
search_repository 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 search_repository 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 search_repository. 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.
search_repository 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.