execute_code
Execute arbitrary Python code inside Blender. Has access to bpy, mathutils, math, os.
This record as markdown: /tools/dwgx-blender-copilot/execute-code.md
What execute_code does on Blender Copilot MCP Server
AI agents invoke execute_code 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 execute_code is rated High
This tool allows running arbitrary Python code within Blender's process, including system-level operations via the 'os' module. An AI agent could use this to modify files, execute system commands, exfiltrate data, or cause uncontrolled changes to the 3D scene or host system.
From the tool's definition Tool explicitly states 'Execute arbitrary Python code inside Blender' with access to 'bpy, mathutils, math, os'. The word 'arbitrary' and inclusion of 'os' module confirms unrestricted code execution capability.
Attacks that exploit this kind of access
The rule that runs execute_code 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 execute_code, this is the rule to start with:
execute_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 Blender Copilot MCP Server, apply this rule, and every execute_code call is checked against it from then on.
Questions about execute_code
Execute arbitrary Python code inside Blender. Has access to bpy, mathutils, math, os. 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 execute_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 Copilot MCP Server. Nothing to install.
execute_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_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_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_code 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