batch_delete
Delete multiple objects at once by their names.
This record as markdown: /tools/dwgx-blender-copilot/batch-delete.md
What batch_delete does on Blender Copilot MCP Server
AI agents call batch_delete 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 batch_delete is rated Critical
This tool irreversibly removes data (Blender scene objects) and cannot be undone through normal tool parameters. While Blender has undo functionality, the tool itself performs a destructive operation. The batch nature increases blast radius—an AI could delete numerous critical assets in a single invocation if arguments are misinterpreted.
From the tool's definition Tool name 'batch_delete' combined with description 'Delete multiple objects at once by their names' explicitly performs deletion of objects. The word 'delete' indicates irreversible removal of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_delete 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 batch_delete, this is the rule to start with:
batch_delete 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 batch_delete call is checked against it from then on.
Questions about batch_delete
Delete multiple objects at once by their names. 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 batch_delete: 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.
batch_delete 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 batch_delete 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 batch_delete. 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.
batch_delete 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