Delete an object from the Blender scene.
AI agents call delete_object to permanently remove resources in BlenderMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of scene objects in Blender is an irreversible operation that cannot be undone by the tool itself (undo stack is separate). While the user could manually undo in Blender, from the MCP tool's perspective this is a destructive action with no rollback capability.
From the tool's definition Tool name 'delete_object' with description 'Delete an object from the Blender scene.' explicitly indicates irreversible removal of data from the scene.
Attacks that exploit this kind of access
Delete an object from the Blender scene. It is categorised as a Destructive tool in the BlenderMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Blender 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 BlenderMCP. 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 MCP server (richard-devbot/blender-mcp-csm). 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 →