Execute Python script in Blender (headless).
AI agents invoke script_execute 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.
This tool allows execution of arbitrary Python scripts within Blender's runtime environment. Even in headless mode, this grants the ability to run code with Blender's full API access, potentially modifying scenes, files, calling external processes, or accessing the filesystem.
From the tool's definition Tool name 'script_execute' combined with description 'Execute Python script in Blender (headless)' explicitly indicates arbitrary code execution capability.
Documented attack patterns abuse exactly the kind of access script_execute gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Blender, and nothing reaches the server without passing your rules. This is the rule we recommend for script_execute:
{
"version": "1",
"default": "deny",
"tools": {
"script_execute": {
"limits": [
{
"counter": "script_execute_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}script_execute 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.
Free to start. No card required.
Execute Python script in Blender (headless). 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 script_execute: 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.
script_execute 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 script_execute 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 script_execute. 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.
script_execute 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.
Start from Blender, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
77 Blender tools catalogued and risk-classified — across an index of 43,000+ MCP servers.