create_list_container
AI agents use create_list_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 container object in RSpace, which is a reversible write operation. While the description is empty (lowering confidence slightly), the naming convention and context of sibling tools clearly indicate data creation rather than deletion, execution of arbitrary code, or financial impact.
From the tool's definition Tool name 'create_list_container' indicates creation of a data structure in RSpace. Sibling tools like 'create_sample', 'create_document_from_form', 'create_grid_container', and 'create_image_container' all create reversible data structures, suggesting this…
Attacks that exploit this kind of access
create_list_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_list_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_list_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_list_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_list_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_list_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 →