blender_open_file
Open a .blend file in the running Blender instance.
This record as markdown: /tools/dwgx-blender-copilot/blender-open-file.md
What blender_open_file does on Blender Copilot MCP Server
AI agents invoke blender_open_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.
Why blender_open_file is rated High
This tool triggers an external operation (opening a file) within a running Blender instance. It doesn't merely read data — it causes Blender to load and execute a .blend file, which can contain embedded scripts and assets. This could lead to arbitrary code execution if a malicious .blend file is opened, making it Execute category with high severity.
From the tool's definition Open a .blend file in the running Blender instance
Attacks that exploit this kind of access
The rule that runs blender_open_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 blender_open_file, this is the rule to start with:
blender_open_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every blender_open_file call is checked against it from then on.
Questions about blender_open_file
Open a .blend file in the running Blender instance. 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.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for blender_open_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.
blender_open_file 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_open_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.
Set action: deny in the PolicyLayer policy for blender_open_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.
blender_open_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.
More on Blender Copilot MCP Server, and thousands of servers like it.
Across the catalogue