Retrieve details of multiple Spaces by their IDs.
AI agents call getSpacesByIds to retrieve information from Xdevplatform/xmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves space metadata by IDs. It queries and returns information without modifying, deleting, or executing any operations. The retrieval of space details is a typical read operation with minimal risk, as it only accesses existing data without altering system state.
From the tool's definition Tool name contains 'get' and description states 'Retrieve details of multiple Spaces by their IDs.' These are characteristic indicators of a read operation with no side effects.
Attacks that exploit this kind of access
Retrieve details of multiple Spaces by their IDs. It is categorised as a Read tool in the Xdevplatform/xmcp MCP Server, which means it retrieves data without modifying state.
Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for getSpacesByIds: 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 Xdevplatform/xmcp. Nothing to install.
getSpacesByIds 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 getSpacesByIds 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 getSpacesByIds. 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.
getSpacesByIds is provided by the Xdevplatform/x MCP server (xdevplatform/xmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
getSpacesByIds is one line of Xdevplatform/x's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →