modifier_remove
Remove a modifier from an object without applying it.
This record as markdown: /tools/dwgx-blender-copilot/modifier-remove.md
What modifier_remove does on Blender Copilot MCP Server
AI agents call modifier_remove 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 modifier_remove is rated Critical
Removing a modifier without applying it is irreversible destruction of that modifier's configuration and effects — it cannot be undone once removed (outside of Blender's undo stack, which an AI agent may not reliably use). The modifier settings and stack position are permanently lost.
From the tool's definition Remove a modifier from an object without applying it
Attacks that exploit this kind of access
The rule that runs modifier_remove 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 modifier_remove, this is the rule to start with:
modifier_remove 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 modifier_remove call is checked against it from then on.
Questions about modifier_remove
Remove a modifier from an object without applying it. 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 modifier_remove: 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.
modifier_remove 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 modifier_remove 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 modifier_remove. 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.
modifier_remove 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