vrc_setup_eye_tracking
Set up VRChat eye tracking: creates eye tracking blend shapes and optionally eye bones.
This record as markdown: /tools/dwgx-blender-copilot/vrc-setup-eye-tracking.md
What vrc_setup_eye_tracking does on Blender Copilot MCP Server
AI agents use vrc_setup_eye_tracking 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_setup_eye_tracking is rated Medium
This tool modifies a Blender project by creating new blend shapes and bones. These are reversible changes (not Destructive), and the tool doesn't execute arbitrary code, trigger external systems, or move data (not Execute). It creates new assets within the 3D model, fitting the Write category. Severity is medium because misuse could require manual cleanup but won't cause permanent data loss.
From the tool's definition Creates eye tracking blend shapes and optionally eye bones - both of which are modifications to the 3D model structure that can be reversed (deleted/reimported) but alter the project state.
Attacks that exploit this kind of access
The rule that runs vrc_setup_eye_tracking 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_setup_eye_tracking, this is the rule to start with:
vrc_setup_eye_tracking 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_setup_eye_tracking call is checked against it from then on.
Questions about vrc_setup_eye_tracking
Set up VRChat eye tracking: creates eye tracking blend shapes and optionally eye bones. 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_setup_eye_tracking: 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_setup_eye_tracking 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_setup_eye_tracking 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_setup_eye_tracking. 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_setup_eye_tracking 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