move_items_to_image_container
AI agents use move_items_to_image_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.
This tool modifies the state of research data by relocating items to different containers, which is a Write-category operation (reversible data modification). The empty description prevents high confidence assessment, but the name and context (RSpace API for research data manipulation, alongside other creation/modification tools) indicate a structural write operation.
From the tool's definition Tool name 'move_items_to_image_container' indicates structural modification of items within RSpace (a research data management system).
Attacks that exploit this kind of access
move_items_to_image_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 move_items_to_image_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.
move_items_to_image_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 move_items_to_image_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 move_items_to_image_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.
move_items_to_image_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 →