execute_blender_code
Execute arbitrary Python code in Blender context. Has access to bpy, C (context), D (data). WARNING: This can modify or delete your scene. Save your work first!
This record as markdown: /tools/aryeon0228-blendermcp/execute-blender-code.md
What execute_blender_code does on BlenderMCP
AI agents invoke execute_blender_code to trigger actions in BlenderMCP. 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 execute_blender_code is rated High
This is an Execute-category tool because it runs arbitrary code whose effects depend entirely on the arguments provided. While the warning mentions potential destruction, the primary capability is code execution with full Blender API access.
From the tool's definition Tool explicitly states 'Execute arbitrary Python code in Blender context' with access to bpy, C (context), and D (data). Warning states 'This can modify or delete your scene.' The tool permits execution of unrestricted Python scripts within Blender's API.
Attacks that exploit this kind of access
The rule that runs execute_blender_code safely
PolicyLayer is an MCP gateway: it sits between your AI agents and BlenderMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For execute_blender_code, this is the rule to start with:
execute_blender_code 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 BlenderMCP, apply this rule, and every execute_blender_code call is checked against it from then on.
Questions about execute_blender_code
Execute arbitrary Python code in Blender context. Has access to bpy, C (context), D (data). WARNING: This can modify or delete your scene. Save your work first!. It is categorised as a Execute tool in the BlenderMCP 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 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 BlenderMCP. 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 server (aryeon0228/blendermcp). 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