remove_modifier
Remove a modifier from an object without applying it.
This record as markdown: /tools/dwgx-blender-copilot/remove-modifier.md
What remove_modifier does on Blender Copilot MCP Server
AI agents call remove_modifier 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 remove_modifier is rated Critical
Removing a modifier without applying it permanently discards the modifier and its configuration from the object. This action is irreversible — the modifier's settings and effects are lost. This qualifies as Destructive since the data cannot be recovered once removed.
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 remove_modifier 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 remove_modifier, this is the rule to start with:
remove_modifier 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 remove_modifier call is checked against it from then on.
Questions about remove_modifier
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 remove_modifier: 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.
remove_modifier 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 remove_modifier 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 remove_modifier. 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.
remove_modifier 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