Get structures and collections of a space
AI agents call get_space_info to retrieve information from Capacities MCP Bridge (Unofficial) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about space structures and collections, which is a read-only operation with no side effects. It querying existing data from the Capacities.io API without creating, modifying, or deleting anything. The low severity reflects minimal blast radius—an agent misusing this would only over-read data.
From the tool's definition Tool name 'get_space_info' and description 'Get structures and collections of a space' indicate retrieval of metadata about a space without modification. The verb 'Get' is explicitly query-oriented.
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 Capacities MCP Bridge (Unofficial), 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 structures and collections of a space. It is categorised as a Read tool in the Capacities MCP Bridge (Unofficial) MCP Server, which means it retrieves data without modifying state.
Register the Capacities MCP Bridge (Unofficial) 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 Capacities MCP Bridge (Unofficial). 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 Capacities MCP Bridge (Unofficial) MCP server (natkitten/capacities-mcp-bridge-unofficial). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Capacities MCP Bridge (Unofficial), 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.
5 Capacities MCP Bridge (Unofficial) tools catalogued and risk-classified — across an index of 43,000+ MCP servers.