pipeline_blender_to_unity
A execute tool on the Blender Copilot MCP server.
This record as markdown: /tools/dwgx-blender-copilot/pipeline-blender-to-unity.md
What pipeline_blender_to_unity does on Blender Copilot MCP Server
AI agents invoke pipeline_blender_to_unity 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 pipeline_blender_to_unity is rated High
The name implies executing a pipeline operation that transfers/exports assets from one application (Blender) to another (Unity). This constitutes an external operation with side effects, likely involving file system writes and potentially launching external processes. With an empty description, confidence is lowered, but the pipeline trigger nature makes Execute the most appropriate category.
From the tool's definition Tool name 'pipeline_blender_to_unity' suggests triggering an export/conversion pipeline from Blender to Unity; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs pipeline_blender_to_unity 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 pipeline_blender_to_unity, this is the rule to start with:
pipeline_blender_to_unity 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 pipeline_blender_to_unity call is checked against it from then on.
Questions about pipeline_blender_to_unity
pipeline_blender_to_unity 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 pipeline_blender_to_unity: 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.
pipeline_blender_to_unity 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 pipeline_blender_to_unity 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 pipeline_blender_to_unity. 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.
pipeline_blender_to_unity 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