vrc_attach_accessory

A execute tool on the Blender Copilot MCP server.

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

This record as markdown: /tools/dwgx-blender-copilot/vrc-attach-accessory.md

What vrc_attach_accessory does on Blender Copilot MCP Server

AI agents invoke vrc_attach_accessory 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 vrc_attach_accessory is rated High

The tool name suggests it attaches an accessory to a VRChat avatar, which likely involves modifying or executing operations within Blender's 3D scene. Given the VRChat avatar pipeline context, this is likely a Write or Execute operation.

From the tool's definition Tool name 'vrc_attach_accessory' and server context 'full VRChat avatar pipeline' — no description provided

Questions about vrc_attach_accessory

What does the vrc_attach_accessory tool do? +

vrc_attach_accessory is a execute tool on the Blender Copilot MCP Server MCP server. 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.

How do I enforce a policy on vrc_attach_accessory? +

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

vrc_attach_accessory is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit vrc_attach_accessory? +

Yes. Add a rate_limit block to the vrc_attach_accessory 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 vrc_attach_accessory completely? +

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

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