blender_geonodes
A execute tool on the Blender MCP server.
This record as markdown: /tools/sandraschi-blender-mcp/blender-geonodes.md
What blender_geonodes does on Blender
AI agents invoke blender_geonodes to trigger actions in Blender. 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 blender_geonodes is rated High
Geometry Nodes in Blender is a procedural system that can create, modify, and execute node-based operations on 3D geometry. Given the server context of AI-powered Blender control, this tool likely executes geometry node workflows which can significantly alter 3D scenes.
From the tool's definition Tool name 'blender_geonodes' suggests Geometry Nodes manipulation in Blender; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs blender_geonodes 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_geonodes, this is the rule to start with:
blender_geonodes 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, apply this rule, and every blender_geonodes call is checked against it from then on.
Questions about blender_geonodes
blender_geonodes is a execute tool on the Blender MCP server. It is categorised as a Execute tool in the Blender MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Blender MCP server in PolicyLayer and add a rule for blender_geonodes: 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_geonodes 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 blender_geonodes 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_geonodes. 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_geonodes 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.
Across the catalogue