delete_object
Delete an object from the scene by name.
This record as markdown: /tools/dwgx-blender-copilot/delete-object.md
What delete_object does on Blender Copilot MCP Server
AI agents call delete_object to permanently remove resources in Blender Copilot MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_object is rated Critical
Deletion of objects in a 3D scene is an irreversible operation that cannot be undone through normal tool use (without relying on Blender's undo system external to this tool).
From the tool's definition Tool name is 'delete_object' with description 'Delete an object from the scene by name.' The verb 'Delete' combined with removal from a scene indicates irreversible data loss.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_object, this is the rule to start with:
delete_object is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every delete_object call is checked against it from then on.
Questions about delete_object
Delete an object from the scene by name. It is categorised as a Destructive tool in the Blender Copilot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_object is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue