blender.export_blend
Queue a portable editable Blender export of the authoritative accepted scene.
This record as markdown: /tools/visionmcp/blender.export-blend.md
What blender.export_blend does on Visionmcp
AI agents use blender.export_blend to create or update resources in Visionmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Visionmcp environment.
Why blender.export_blend is rated Medium
This tool exports/writes a Blender file from an existing scene. It creates a new exported artifact (a .blend file) from the accepted scene, which is a Write operation — it generates/outputs data without destructively modifying source data. Severity is medium because it involves exporting authoritative scene data, but misuse is limited to producing unwanted file exports.
From the tool's definition Queue a portable editable Blender export of the authoritative accepted scene
Attacks that exploit this kind of access
The rule that runs blender.export_blend safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender.export_blend, this is the rule to start with:
blender.export_blend stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Visionmcp, apply this rule, and every blender.export_blend call is checked against it from then on.
Questions about blender.export_blend
Queue a portable editable Blender export of the authoritative accepted scene. It is categorised as a Write tool in the Visionmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vision MCP server in PolicyLayer and add a rule for blender.export_blend: 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 Visionmcp. Nothing to install.
blender.export_blend is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the blender.export_blend 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.export_blend. 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.export_blend is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
This server
Across the catalogue