unity_build_avatar
Trigger VRC SDK avatar build (local test build, not publish).
This record as markdown: /tools/dwgx-blender-copilot/unity-build-avatar.md
What unity_build_avatar does on Blender Copilot MCP Server
AI agents invoke unity_build_avatar to trigger actions in Blender Copilot MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why unity_build_avatar is rated High
This tool invokes an external build system (VRC SDK) to compile and generate VRChat avatar assets. While scoped to 'local test build', it still executes a complex, externally-dependent operation that could consume resources, create files, or fail in unpredictable ways. Misuse could cause build failures, resource exhaustion, or generation of malformed avatars.
From the tool's definition Trigger VRC SDK avatar build (local test build, not publish). The verb 'trigger' and 'build' indicate this tool executes an external operation (VRC SDK build process) whose effects depend on arguments and system state.
Attacks that exploit this kind of access
The rule that runs unity_build_avatar 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 unity_build_avatar, this is the rule to start with:
unity_build_avatar stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 unity_build_avatar call is checked against it from then on.
Questions about unity_build_avatar
Trigger VRC SDK avatar build (local test build, not publish). It is categorised as a Execute tool in the Blender Copilot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for unity_build_avatar: 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.
unity_build_avatar is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the unity_build_avatar 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 unity_build_avatar. 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.
unity_build_avatar 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