ft_mirror_shape_key
A write tool on the Blender Copilot MCP server.
This record as markdown: /tools/dwgx-blender-copilot/ft-mirror-shape-key.md
What ft_mirror_shape_key does on Blender Copilot MCP Server
AI agents use ft_mirror_shape_key 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 ft_mirror_shape_key is rated Medium
The tool modifies shape key data (a reversible property in Blender that controls vertex deformations), placing it in the Write category. No description provided lowers confidence slightly, but the naming pattern and server context (3D creation tools) suggest this creates or modifies shape key mirror symmetry settings rather than executing arbitrary code or permanently deleting data.
From the tool's definition Tool name 'ft_mirror_shape_key' indicates modification of shape key data in Blender; sibling tools like 'add_cloth', 'add_constraint', 'add_modifier' consistently perform reversible write operations on scene geometry and properties.
Attacks that exploit this kind of access
The rule that runs ft_mirror_shape_key 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_mirror_shape_key, this is the rule to start with:
ft_mirror_shape_key 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 ft_mirror_shape_key call is checked against it from then on.
Questions about ft_mirror_shape_key
ft_mirror_shape_key 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 ft_mirror_shape_key: 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_mirror_shape_key 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 ft_mirror_shape_key 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_mirror_shape_key. 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_mirror_shape_key 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