Get detailed information about a specific Datasphere space
AI agents call get_space_info 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 tool performs a read-only query operation that retrieves existing information about a Datasphere space. It has no side effects, does not modify data, execute code, delete resources, or involve financial transactions. While the server operates on production tenant data, this specific tool is scoped to information retrieval only, making it a straightforward Read classification.
From the tool's definition Tool name is 'get_space_info' and description states 'Get detailed information about a specific Datasphere space' — this retrieves metadata/information about a space with no modification, creation, deletion, code execution, or financial impact.
Documented attack patterns abuse exactly the kind of access get_space_info 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 get_space_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_space_info": {}
}
} get_space_info 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.
Get detailed information about a specific Datasphere 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 get_space_info: 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.
get_space_info 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_space_info 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_space_info. 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_space_info 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.