generate_blender_script

What generate_blender_script does on Blender

AI agents invoke generate_blender_script 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.

Why generate_blender_script is rated High

The tool name implies generating a Blender script, and in context of this MCP server that automates Blender operations, generated scripts are almost certainly executed within Blender. This falls under Execute as it runs code/scripts. The description is empty, reducing confidence, but the server context and naming strongly suggest script generation and likely execution.

From the tool's definition Tool name 'generate_blender_script' on a server that enables AI-powered control of Blender to 'create, manipulate, and automate 3D scenes'; sibling tools include 'agentic_blender_workflow' and 'blender_batch' suggesting script execution capabilities.

The rule that runs generate_blender_script safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Blender, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_blender_script, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_blender_script": {
      "limits": [
        {
          "counter": "generate_blender_script_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about generate_blender_script