Execute an arbitrary Blender Python script. Use for advanced operations not covered by other tools.
AI agents invoke blender_execute_script to trigger actions in Polybridge MCP. 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 executes arbitrary Python scripts within Blender, a 3D graphics application with powerful computational capabilities. Arbitrary script execution is inherently Execute-class behavior. The 'arbitrary' qualifier and 'advanced operations' framing indicate unrestricted code execution.
From the tool's definition Execute an arbitrary Blender Python script. Use for advanced operations not covered by other tools.
Attacks that exploit this kind of access
Execute an arbitrary Blender Python script. Use for advanced operations not covered by other tools. It is categorised as a Execute tool in the Polybridge MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Polybridge MCP server in PolicyLayer and add a rule for blender_execute_script: 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 Polybridge MCP. Nothing to install.
blender_execute_script 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_execute_script 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_execute_script. 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_execute_script is provided by the Polybridge MCP server (madjeek-web/polybridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →