Delete an object from the Blender scene.
AI agents call delete_object to permanently remove resources in Blender MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of objects from a Blender scene is irreversible and cannot be undone by the tool itself (undo would require user intervention). This falls under the Destructive category as it permanently removes data. Severity is high because an AI agent could delete critical scene assets, though the blast radius is limited to the Blender project scope rather than system-wide or cross-application damage.
From the tool's definition Tool name is 'delete_object' with description 'Delete an object from the Blender scene.' The verb 'delete' 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 Blender MCP 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 Blender MCP. 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 (nowcika/blender_mcp). 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 →