set_collection_visibility
Set viewport and render visibility of a collection and all its objects.
This record as markdown: /tools/dwgx-blender-copilot/set-collection-visibility.md
What set_collection_visibility does on Blender Copilot MCP Server
AI agents use set_collection_visibility to create or update resources in Blender Copilot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender Copilot MCP Server environment.
Why set_collection_visibility is rated Medium
This tool changes visibility properties of collections and objects in Blender, which is a write operation that modifies scene state. The change is reversible (visibility can be toggled back), so it does not qualify as Destructive. The blast radius is medium because incorrect visibility changes could hide critical scene elements, affecting the user's workflow, but the change is easily undone.
From the tool's definition The tool description states it 'Set[s] viewport and render visibility of a collection and all its objects.' This modifies the visibility state of objects in a Blender scene, which is a reversible change to scene properties rather than permanent data deletion.
Attacks that exploit this kind of access
The rule that runs set_collection_visibility safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Blender Copilot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_collection_visibility, this is the rule to start with:
set_collection_visibility 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 Blender Copilot MCP Server, apply this rule, and every set_collection_visibility call is checked against it from then on.
Questions about set_collection_visibility
Set viewport and render visibility of a collection and all its objects. It is categorised as a Write tool in the Blender Copilot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for set_collection_visibility: 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 Blender Copilot MCP Server. Nothing to install.
set_collection_visibility 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 set_collection_visibility 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 set_collection_visibility. 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.
set_collection_visibility is provided by the Blender Copilot MCP Server MCP server (dwgx/blender-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender Copilot MCP Server, and thousands of servers like it.
This server
Across the catalogue