ft_setup_eye_tracking_full
A execute tool on the Blender Copilot MCP server.
This record as markdown: /tools/dwgx-blender-copilot/ft-setup-eye-tracking-full.md
What ft_setup_eye_tracking_full does on Blender Copilot MCP Server
AI agents invoke ft_setup_eye_tracking_full 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 ft_setup_eye_tracking_full is rated High
The tool name suggests it performs a full setup of eye tracking, likely as part of the VRChat avatar pipeline. 'Setup' operations typically involve writing configuration, modifying object properties, and potentially executing scripts in Blender. Given the 'full' qualifier it likely makes multiple changes.
From the tool's definition Tool name 'ft_setup_eye_tracking_full' and server context (VRChat avatar pipeline, 308 tools across 25 modules). Description is empty.
Attacks that exploit this kind of access
The rule that runs ft_setup_eye_tracking_full 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 ft_setup_eye_tracking_full, this is the rule to start with:
ft_setup_eye_tracking_full 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 ft_setup_eye_tracking_full call is checked against it from then on.
Questions about ft_setup_eye_tracking_full
ft_setup_eye_tracking_full 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.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for ft_setup_eye_tracking_full: 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.
ft_setup_eye_tracking_full 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 ft_setup_eye_tracking_full 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 ft_setup_eye_tracking_full. 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.
ft_setup_eye_tracking_full 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