Automatically organize scene assets into collections based on object type. This intelligent organization tool creates collections for different asset types (models, materials, etc.) and moves objects accordingly. Args: - create_collections (boolean, default true): Create collections for each asse...
AI agents use blender_organize_assets_by_type 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 modifies scene structure and object properties (collections and names) in a reversible manner. Creating collections and moving objects are Write operations—they change state but can be undone in Blender.
From the tool's definition Tool description states it 'creates collections' and 'moves objects accordingly'. The parameters include 'create_collections' (boolean to create collections) and the function organizes/modifies scene structure by moving objects into collections and optionally…
Attacks that exploit this kind of access
Automatically organize scene assets into collections based on object type. This intelligent organization tool creates collections for different asset types (models, materials, etc.) and moves objects accordingly. Args: - create_collections (boolean, default true): Create collections for each asset type - existing_objects_only (boolean, default true): Only organize existing objects - prefix_with_type (boolean, default false): Prefix object names with asset type Returns: Organization summary with collections created and objects moved Examples: - Basic organization: create_collections=true, existing_objects_only=true, prefix_with_type=false - Include new objects: create_collections=true, existing_objects_only=false - Naming convention: create_collections=true, prefix_with_type=true Use when: Cleaning up disorganized scenes, establishing asset workflows, improving scene management Don. 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_organize_assets_by_type: 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_organize_assets_by_type 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_organize_assets_by_type 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_organize_assets_by_type. 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_organize_assets_by_type 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 →