Get a list of all personal spaces in Capacities
AI agents call capacities_list_spaces to retrieve information from Capacities 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 and enumerates existing spaces without creating, modifying, deleting, or executing any operations. It is a straightforward query that returns data about the user's spaces. The blast radius of misuse is minimal—an agent could only discover what spaces exist, which is informational only.
From the tool's definition Tool name 'capacities_list_spaces' and description 'Get a list of all personal spaces in Capacities' indicate a retrieval operation with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access capacities_list_spaces gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Capacities MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for capacities_list_spaces:
{
"version": "1",
"default": "deny",
"tools": {
"capacities_list_spaces": {}
}
} capacities_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.
Get a list of all personal spaces in Capacities. It is categorised as a Read tool in the Capacities MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Capacities MCP Server MCP server in PolicyLayer and add a rule for capacities_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 Capacities MCP Server. Nothing to install.
capacities_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 capacities_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 capacities_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.
capacities_list_spaces is provided by the Capacities MCP Server MCP server (jem-computer/capacities-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Capacities 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.
6 Capacities MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.