AI agents invoke blender_exec to trigger actions in Blender MCP Bridge. 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.
The name 'blender_exec' strongly implies execution of arbitrary code within Blender's Python environment. The server description explicitly mentions executing Python scripts and directly interacting with Blender's internal environment. Arbitrary Python execution has critical blast radius as it can read/write files, run system commands, and cause irreversible damage.
From the tool's definition Tool name 'blender_exec' on a server described as enabling 'execute Python scripts' and 'remote control of Blender'
Documented attack patterns abuse exactly the kind of access blender_exec gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Blender MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for blender_exec:
{
"version": "1",
"default": "deny",
"tools": {
"blender_exec": {
"limits": [
{
"counter": "blender_exec_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}blender_exec 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.
blender_exec. It is categorised as a Execute tool in the Blender MCP Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Blender MCP Bridge MCP server in PolicyLayer and add a rule for blender_exec: 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 Bridge. Nothing to install.
blender_exec 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 blender_exec 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 blender_exec. 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.
blender_exec is provided by the Blender MCP Bridge MCP server (mithran-balachander/blender-mcp-antigravity). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Blender MCP Bridge, 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.
3 Blender MCP Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.