This record as markdown: /tools/xdevplatform-xmcp/searchspaces.md
What searchSpaces does on Xdevplatform/xmcp
AI agents call searchSpaces to retrieve information from Xdevplatform/xmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why searchSpaces is rated Low
This tool performs a search operation to retrieve information about Spaces matching specified criteria. It is a read-only operation with no side effects, no code execution, no data modification, and no financial implications. The low severity reflects minimal risk if misused by an AI agent—search results alone cannot cause harm.
From the tool's definition Tool name 'searchSpaces' and description 'Search for Spaces by title or keyword' indicate a query operation that retrieves data without modifying or deleting it.
Attacks that exploit this kind of access
The rule that runs searchSpaces safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Xdevplatform/xmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For searchSpaces, this is the rule to start with:
searchSpaces is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Xdevplatform/xmcp, apply this rule, and every searchSpaces call is checked against it from then on.
Questions about searchSpaces
Search for Spaces by title or keyword. 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 searchSpaces: 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.
searchSpaces 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 searchSpaces 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 searchSpaces. 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.
searchSpaces 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.
More on Xdevplatform/x, and thousands of servers like it.
This server
Across the catalogue