This record as markdown: /tools/sandraschi-blender-mcp/blender-rigging.md
What blender_rigging does on Blender
AI agents call blender_rigging as a supporting operation in Blender workflows.
Why blender_rigging is rated Low
The description is empty and uninformative. The name 'blender_rigging' suggests it relates to rigging operations in Blender (setting up armatures/bones for animation), which would likely be a Write operation. However, given the empty description and the broader server context that includes Execute-level tools like 'agentic_blender_workflow', confidence is very low.
From the tool's definition Tool name is 'blender_rigging' with an empty description. No description provided to assess actual behavior.
Attacks that exploit this kind of access
The rule that runs blender_rigging safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Blender, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender_rigging, this is the rule to start with:
blender_rigging gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender, apply this rule, and every blender_rigging call is checked against it from then on.
Questions about blender_rigging
blender_rigging is a other tool on the Blender MCP server. It is categorised as a Other tool in the Blender MCP Server, which means it performs auxiliary operations.
Register the Blender MCP server in PolicyLayer and add a rule for blender_rigging: 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. Nothing to install.
blender_rigging is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the blender_rigging 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 blender_rigging. 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.
blender_rigging is provided by the Blender MCP server (sandraschi/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender, and thousands of servers like it.
This server
Across the catalogue