vrc_merge_materials
A write tool on the Blender Copilot MCP server.
This record as markdown: /tools/dwgx-blender-copilot/vrc-merge-materials.md
What vrc_merge_materials does on Blender Copilot MCP Server
AI agents use vrc_merge_materials to create or update resources in Blender Copilot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender Copilot MCP Server environment.
Why vrc_merge_materials is rated Medium
Merging materials modifies data in a Blender scene reversibly—combined materials can be separated or undone via undo functionality. This is characteristic of Write operations. Severity is medium because unintended material merges could degrade a 3D asset's appearance or workflow, but changes are not destructive (no deletion) and have no financial impact.
From the tool's definition Tool name 'vrc_merge_materials' indicates modification of materials within a VRChat avatar pipeline context. No description provided, but the verb 'merge' implies combining or modifying existing material data.
Attacks that exploit this kind of access
The rule that runs vrc_merge_materials 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 vrc_merge_materials, this is the rule to start with:
vrc_merge_materials stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every vrc_merge_materials call is checked against it from then on.
Questions about vrc_merge_materials
vrc_merge_materials is a write tool on the Blender Copilot MCP Server MCP server. It is categorised as a Write tool in the Blender Copilot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for vrc_merge_materials: 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.
vrc_merge_materials is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vrc_merge_materials 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 vrc_merge_materials. 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.
vrc_merge_materials 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.
This server
Across the catalogue