blender.import_model
Import a Rhino-exported model into Blender
This record as markdown: /tools/cowork-os/blender.import-model.md
What blender.import_model does on CoWork OS
AI agents use blender.import_model to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why blender.import_model is rated Medium
Importing a model is a write operation that modifies the Blender scene/project in a reversible way. It adds data structures (meshes, materials, etc.) to the active Blender file but does not execute arbitrary code, delete data, or trigger external financial transactions. The operation can be undone, making it Write rather than Destructive.
From the tool's definition Tool imports/loads a model file into Blender, modifying the current Blender project state by adding new 3D geometry and assets.
Attacks that exploit this kind of access
The rule that runs blender.import_model safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender.import_model, this is the rule to start with:
blender.import_model 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 CoWork OS, apply this rule, and every blender.import_model call is checked against it from then on.
Questions about blender.import_model
Import a Rhino-exported model into Blender. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for blender.import_model: 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 CoWork OS. Nothing to install.
blender.import_model 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.import_model 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.import_model. 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.import_model is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue