Import a 3D model from CSM.ai into the Blender scene.
AI agents use import_csm_model to create or update resources in BlenderMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BlenderMCP environment.
This tool creates new data (3D model objects) in the Blender scene, which is reversible via undo or deletion. It does not execute arbitrary code, delete existing data, or cause financial impact. The moderate severity reflects that importing large or malicious models could degrade performance or consume resources, but the operation itself is non-destructive and can be undone.
From the tool's definition Tool name 'import_csm_model' and description 'Import a 3D model from CSM.ai into the Blender scene' indicates creation/modification of scene data by adding new objects to the active Blender project.
Attacks that exploit this kind of access
Import a 3D model from CSM.ai into the Blender scene. It is categorised as a Write tool in the BlenderMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender MCP server in PolicyLayer and add a rule for import_csm_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 BlenderMCP. Nothing to install.
import_csm_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 import_csm_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 import_csm_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.
import_csm_model is provided by the Blender MCP server (richard-devbot/blender-mcp-csm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →