unity_setup_gesture_layer
A write tool on the Blender Copilot MCP server.
This record as markdown: /tools/dwgx-blender-copilot/unity-setup-gesture-layer.md
What unity_setup_gesture_layer does on Blender Copilot MCP Server
AI agents use unity_setup_gesture_layer 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 unity_setup_gesture_layer is rated Medium
The tool appears to set up or create a gesture layer configuration, which is a reversible modification to a scene or avatar structure. Without a description, confidence is moderate. This fits Write (creates/modifies data reversibly) rather than Execute (no arbitrary code execution evident from name) or Destructive (setup implies non-destructive action).
From the tool's definition Tool name 'unity_setup_gesture_layer' indicates creation or configuration of a gesture layer in a Unity/VRChat context. Sibling tools like 'add_cloth', 'add_constraint', 'add_modifier' are clearly Write operations that create/modify scene objects.
Attacks that exploit this kind of access
The rule that runs unity_setup_gesture_layer 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_setup_gesture_layer, this is the rule to start with:
unity_setup_gesture_layer 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 unity_setup_gesture_layer call is checked against it from then on.
Questions about unity_setup_gesture_layer
unity_setup_gesture_layer 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 unity_setup_gesture_layer: 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_setup_gesture_layer 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 unity_setup_gesture_layer 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_setup_gesture_layer. 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_setup_gesture_layer 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