move_to_collection
Move an object to a different collection. Removes from current collection(s).
This record as markdown: /tools/dwgx-blender-copilot/move-to-collection.md
What move_to_collection does on Blender Copilot MCP Server
AI agents use move_to_collection to create or update resources in Blender Copilot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender Copilot MCP Server environment.
Why move_to_collection is rated Medium
The tool modifies scene metadata (object collection membership) reversibly. It does not delete objects, execute code, move money, or trigger external operations. It is a Write operation because it reorganizes data structure without destruction.
From the tool's definition Move an object to a different collection. Removes from current collection(s). - This modifies the organizational structure of the Blender scene by relocating objects between collections, which is reversible.
Attacks that exploit this kind of access
The rule that runs move_to_collection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Blender Copilot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_to_collection, this is the rule to start with:
move_to_collection stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every move_to_collection call is checked against it from then on.
Questions about move_to_collection
Move an object to a different collection. Removes from current collection(s). It is categorised as a Write tool in the Blender Copilot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for move_to_collection: 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 Blender Copilot MCP Server. Nothing to install.
move_to_collection 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_to_collection 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_to_collection. 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_to_collection is provided by the Blender Copilot MCP Server MCP server (dwgx/blender-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender Copilot MCP Server, and thousands of servers like it.
This server
Across the catalogue