scene_cleanup
Clean up unused data blocks from the scene.
This record as markdown: /tools/dwgx-blender-copilot/scene-cleanup.md
What scene_cleanup does on Blender Copilot MCP Server
AI agents call scene_cleanup 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 scene_cleanup is rated Critical
Removing/purging unused data blocks is an irreversible destructive operation — once data blocks are cleaned up from the scene, they cannot be recovered without an undo or backup. This qualifies as Destructive rather than Write since the operation purges data permanently.
From the tool's definition Clean up unused data blocks from the scene
Attacks that exploit this kind of access
The rule that runs scene_cleanup 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 scene_cleanup, this is the rule to start with:
scene_cleanup 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 scene_cleanup call is checked against it from then on.
Questions about scene_cleanup
Clean up unused data blocks from the scene. 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 scene_cleanup: 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.
scene_cleanup 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 scene_cleanup 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 scene_cleanup. 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.
scene_cleanup 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