uv_remove_layer

Remove a UV layer from an object.

SERVERBlender Copilot MCP Server SOURCEdwgx/blender-copilot
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dwgx-blender-copilot/uv-remove-layer.md

What uv_remove_layer does on Blender Copilot MCP Server

AI agents call uv_remove_layer 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 uv_remove_layer is rated Critical

This tool irreversibly deletes UV layer data from a 3D object. UV layers are critical for texture mapping and their removal cannot be undone programmatically without access to version history. An AI agent misusing this could destroy the texture mapping work of an entire 3D asset, requiring manual recreation. This constitutes data destruction with no built-in recovery mechanism within the tool's scope.

From the tool's definition Tool name 'uv_remove_layer' explicitly removes a UV layer from an object. The verb 'remove' indicates deletion of data. UV layers in Blender are essential texture mapping data that cannot be easily recovered once deleted.

Questions about uv_remove_layer

What does the uv_remove_layer tool do? +

Remove a UV layer from an object. 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.

How do I enforce a policy on uv_remove_layer? +

Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for uv_remove_layer: 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.

What risk level is uv_remove_layer? +

uv_remove_layer is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit uv_remove_layer? +

Yes. Add a rate_limit block to the uv_remove_layer 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.

How do I block uv_remove_layer completely? +

Set action: deny in the PolicyLayer policy for uv_remove_layer. 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.

What MCP server provides uv_remove_layer? +

uv_remove_layer 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Blender Copilot MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.