Import external 3D assets into Blender scene with comprehensive options. Supports multiple 3D file formats including FBX, OBJ, GLTF, and more with advanced import options. Args: - file_path (string): Path to asset file to import (relative to project) - format (optional): Asset format (auto-detect...
AI agents use blender_import_asset to create or update resources in ClaudeKit Blender MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClaudeKit Blender MCP environment.
This tool performs a Write operation: it imports and inserts 3D assets into a Blender scene, creating new scene objects. While reversible (assets can be deleted), the modification is material enough to warrant Write classification.
From the tool's definition "Import external 3D assets into Blender scene" and "Import confirmation with object details" — the tool creates or adds new objects/data to the Blender scene, modifying its state reversibly.
Attacks that exploit this kind of access
Import external 3D assets into Blender scene with comprehensive options. Supports multiple 3D file formats including FBX, OBJ, GLTF, and more with advanced import options. Args: - file_path (string): Path to asset file to import (relative to project) - format (optional): Asset format (auto-detected if not specified) - options (optional): Import options including location, rotation, scale, and processing Returns: Import confirmation with object details and processing information Examples: - Basic import: file_path=. It is categorised as a Write tool in the ClaudeKit Blender MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClaudeKit Blender MCP server in PolicyLayer and add a rule for blender_import_asset: 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 ClaudeKit Blender MCP. Nothing to install.
blender_import_asset 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_asset 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_asset. 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_asset is provided by the ClaudeKit Blender MCP server (olbboy/claudekit-blender-mcp). 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 →