List all Datasphere spaces with their status and metadata
AI agents call list_spaces 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 tool retrieves organizational/metadata information about Datasphere spaces. While it doesn't modify or delete data, it has medium severity because listing spaces could reveal sensitive organizational structure, access patterns, or asset inventory to an AI agent that could be used for reconnaissance in a compromised context.
From the tool's definition Tool name 'list_spaces' and description 'List all Datasphere spaces with their status and metadata' indicate a query operation that retrieves information without modifying data. The verb 'list' and 'get metadata' are typical Read operations.
Documented attack patterns abuse exactly the kind of access list_spaces 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_spaces:
{
"version": "1",
"default": "deny",
"tools": {
"list_spaces": {}
}
} list_spaces 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.
List all Datasphere spaces with their status and metadata. 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_spaces: 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_spaces 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_spaces 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_spaces. 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_spaces 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.