List all collections in the current Blender scene with optional object details. Provides comprehensive view of scene organization structure, including nested collections and object membership. Args: - include_objects (boolean, default false): Include objects in each collection - object_details (b...
AI agents call blender_list_collections to retrieve information from ClaudeKit Blender MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays information about collections and objects in a Blender scene. It has no side effects, does not modify any data, and is explicitly a read-only operation. The include_objects and object_details parameters only control what information is returned, not any actions performed. This is a straightforward data retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'List all collections' and 'Provides comprehensive view of scene organization structure' with optional object details.
Attacks that exploit this kind of access
List all collections in the current Blender scene with optional object details. Provides comprehensive view of scene organization structure, including nested collections and object membership. Args: - include_objects (boolean, default false): Include objects in each collection - object_details (boolean, default false): Include detailed object information Returns: Hierarchical list of collections with optional object details and statistics Examples: - Simple list: include_objects=false, object_details=false - With objects: include_objects=true, object_details=false - Full details: include_objects=true, object_details=true Use when: Understanding scene structure, managing assets, planning organization Don. It is categorised as a Read tool in the ClaudeKit Blender MCP MCP Server, which means it retrieves data without modifying state.
Register the ClaudeKit Blender MCP server in PolicyLayer and add a rule for blender_list_collections: 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_list_collections is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the blender_list_collections 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_list_collections. 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_list_collections 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 →