Retrieves container metadata without content for fast queries
AI agents call get_container_summary to retrieve information from RSpace 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 metadata about containers in RSpace without accessing their actual content, and performs no write, delete, or executable operations. It is a straightforward data retrieval function with minimal risk if misused by an AI agent, as it only exposes metadata that would typically be visible to an authenticated user.
From the tool's definition Tool name 'get_container_summary' and description 'Retrieves container metadata without content for fast queries' indicate a read-only operation that fetches data without modification.
Attacks that exploit this kind of access
Retrieves container metadata without content for fast queries. It is categorised as a Read tool in the RSpace MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RSpace MCP Server MCP server in PolicyLayer and add a rule for get_container_summary: 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 RSpace MCP Server. Nothing to install.
get_container_summary 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_container_summary 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_container_summary. 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_container_summary is provided by the RSpace MCP Server MCP server (rspace-os/rspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →