AI agents call blender_rigging as a supporting operation in Blender workflows.
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.
Documented attack patterns abuse exactly the kind of access blender_rigging gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Blender, and nothing reaches the server without passing your rules. This is the rule we recommend for blender_rigging:
{
"version": "1",
"default": "deny",
"tools": {
"blender_rigging": {
"limits": [
{
"counter": "blender_rigging_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}blender_rigging gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
blender_rigging. 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.
Start from Blender, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
77 Blender tools catalogued and risk-classified — across an index of 43,000+ MCP servers.