separate_object
Separate an object into multiple objects.
This record as markdown: /tools/dwgx-blender-copilot/separate-object.md
What separate_object does on Blender Copilot MCP Server
AI agents use separate_object 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 separate_object is rated Medium
This tool modifies the 3D scene by splitting one object into multiple objects—a creative/structural change that is reversible (objects can be joined back together). It does not execute arbitrary code, delete data irreversibly, or trigger external financial operations. The blast radius is limited to the current Blender project; an agent could create unwanted scene complexity, but the user can undo or rejoin objects.
From the tool's definition Tool name 'separate_object' and description 'Separate an object into multiple objects' indicate a reversible modification operation that transforms scene geometry without deleting data.
Attacks that exploit this kind of access
The rule that runs separate_object 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 separate_object, this is the rule to start with:
separate_object 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 separate_object call is checked against it from then on.
Questions about separate_object
Separate an object into multiple objects. 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 separate_object: 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.
separate_object 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 separate_object 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 separate_object. 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.
separate_object 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