geonodes_add_node
A execute tool on the Blender Copilot MCP server.
This record as markdown: /tools/dwgx-blender-copilot/geonodes-add-node.md
What geonodes_add_node does on Blender Copilot MCP Server
AI agents invoke geonodes_add_node to trigger actions in Blender Copilot MCP Server. 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 geonodes_add_node is rated High
Based on the name, this tool likely adds a node to a Blender geometry nodes network, which is a Write/Execute operation within a 3D creation context. Without a description, confidence is low. Given the broader server context of Blender operations and sibling tools that perform actions (add_modifier, add_constraint, etc.), this is likely a Write or Execute operation.
From the tool's definition Tool name 'geonodes_add_node' suggests adding a node to a geometry nodes graph in Blender; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs geonodes_add_node 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 geonodes_add_node, this is the rule to start with:
geonodes_add_node 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 Copilot MCP Server, apply this rule, and every geonodes_add_node call is checked against it from then on.
Questions about geonodes_add_node
geonodes_add_node is a execute tool on the Blender Copilot MCP Server MCP server. It is categorised as a Execute tool in the Blender Copilot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for geonodes_add_node: 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.
geonodes_add_node 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 geonodes_add_node 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 geonodes_add_node. 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.
geonodes_add_node 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.
Across the catalogue