execute_script_on_file

Execute Python code on an existing .blend file in headless mode.

SERVERBlender Copilot MCP Server SOURCEdwgx/blender-copilot

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dwgx-blender-copilot/execute-script-on-file.md

WHAT IT DOES

What execute_script_on_file does on Blender Copilot MCP Server

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

RISK

Why execute_script_on_file is rated High

This tool allows running arbitrary Python scripts within Blender's context on any .blend file. While not Financial or Destructive by itself (the destruction depends on script content), it is Execute because it triggers external operations (Blender headless execution) whose effects are determined by user-supplied code arguments.

From the tool's definition Tool enables 'Execute Python code on an existing .blend file in headless mode.' Python execution on external files is a classic Execute pattern—the effects depend entirely on the arbitrary code argument.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs execute_script_on_file 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_script_on_file, this is the rule to start with:

execute_script_on_file Rate-limited

execute_script_on_file 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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every execute_script_on_file call is checked against it from then on.

FAQ

Questions about execute_script_on_file

What does the execute_script_on_file tool do? +

Execute Python code on an existing .blend file in headless mode. 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.

How do I enforce a policy on execute_script_on_file? +

Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for execute_script_on_file: 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.

What risk level is execute_script_on_file? +

execute_script_on_file is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_script_on_file? +

Yes. Add a rate_limit block to the execute_script_on_file 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.

How do I block execute_script_on_file completely? +

Set action: deny in the PolicyLayer policy for execute_script_on_file. 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.

What MCP server provides execute_script_on_file? +

execute_script_on_file 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.

KEEP EXPLORING

More on Blender Copilot MCP Server, and thousands of servers like it.

This server

All 307 Blender Copilot MCP Server tools → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server →load_script on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →