io_export_obj
A write tool on the Blender Copilot MCP server.
This record as markdown: /tools/dwgx-blender-copilot/io-export-obj.md
What io_export_obj does on Blender Copilot MCP Server
AI agents use io_export_obj to create or update resources in Blender Copilot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender Copilot MCP Server environment.
Why io_export_obj is rated Medium
Export operations create or write files to disk, which is a Write action (reversible—exported files can be deleted). It is not Destructive because the original Blender scene remains intact. Severity is medium because exporting could expose or write sensitive 3D assets, but the blast radius is limited to file I/O unless the export path is attacker-controlled in a way that overwrites critical files.
From the tool's definition Tool name 'io_export_obj' indicates export functionality. In Blender, export tools create new files by writing 3D scene data to disk in OBJ format.
Attacks that exploit this kind of access
The rule that runs io_export_obj 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 io_export_obj, this is the rule to start with:
io_export_obj 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 Blender Copilot MCP Server, apply this rule, and every io_export_obj call is checked against it from then on.
Questions about io_export_obj
io_export_obj is a write tool on the Blender Copilot MCP Server MCP server. It is categorised as a Write tool in the Blender Copilot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for io_export_obj: 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.
io_export_obj 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 io_export_obj 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 io_export_obj. 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.
io_export_obj 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.
This server
Across the catalogue