execute_blender_code
AI agents invoke execute_blender_code to trigger actions in Blender Mcp Enhanced. 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.
execute_blender_code triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
execute_blender_code. It is categorised as a Execute tool in the Blender Mcp Enhanced MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Blender Mcp Enhanced MCP server in PolicyLayer and add a rule for execute_blender_code: 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 Mcp Enhanced. Nothing to install.
execute_blender_code 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 execute_blender_code 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 execute_blender_code. 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.
execute_blender_code is provided by the Blender Mcp Enhanced MCP server (zachhandley/blender-mcp-enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.