blender_launch
A execute tool on the Blender Copilot MCP server.
This record as markdown: /tools/dwgx-blender-copilot/blender-launch.md
What blender_launch does on Blender Copilot MCP Server
AI agents invoke blender_launch 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_launch is rated High
Launching Blender triggers an external process whose behavior and side effects depend on system state, Blender configuration, and subsequent commands. This is not a passive read operation. While not immediately destructive, it executes code/processes external to the MCP server.
From the tool's definition Tool name 'blender_launch' from Blender Copilot MCP Server indicates launching/starting the Blender application. Description is empty, but context from sibling tools (add_cloth, add_modifier, etc.) and server purpose confirm this is an operation control tool.
Attacks that exploit this kind of access
The rule that runs blender_launch 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_launch, this is the rule to start with:
blender_launch 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_launch call is checked against it from then on.
Questions about blender_launch
blender_launch is a execute tool on the Blender Copilot MCP Server MCP server. 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_launch: 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_launch 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_launch 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_launch. 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_launch 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