create_grid_container
AI agents use create_grid_container to create or update resources in RSpace MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RSpace MCP Server environment.
The tool creates a new grid container in RSpace, which adds data to the research management system. This is a reversible Write operation—containers can be deleted or modified later. Severity is high because bulk creation of containers could pollute the research database or consume storage resources, affecting data integrity and availability for legitimate research workflows.
From the tool's definition Tool name 'create_grid_container' indicates creation of a new container object. Sibling tools on this server (create_document_from_form, create_form, create_image_container, create_list_container, create_sample) all perform Write operations that create…
Attacks that exploit this kind of access
create_grid_container. It is categorised as a Write tool in the RSpace MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RSpace MCP Server MCP server in PolicyLayer and add a rule for create_grid_container: 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.
create_grid_container is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_grid_container 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 create_grid_container. 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.
create_grid_container 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 →