This record as markdown: /tools/aryeon0228-blendermcp/delete-object.md
What delete_object does on BlenderMCP
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.
Why delete_object is rated Critical
Deletion of scene objects in Blender cannot be undone by the tool itself (undo would require separate action). While the blast radius is limited to a single 3D project file rather than critical infrastructure, the action is irreversible and destructive in nature. An AI agent could accidentally or maliciously remove important 3D assets, requiring manual restoration.
From the tool's definition Tool name is 'delete_object' and description states 'Delete an object from the scene' — the verb 'delete' combined with removal from a scene constitutes irreversible data destruction.
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 BlenderMCP, 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 BlenderMCP, 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. 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 (aryeon0228/blendermcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender, and thousands of servers like it.
Across the catalogue