scene_set_visibility
Set object visibility in viewport and render.
This record as markdown: /tools/dwgx-blender-copilot/scene-set-visibility.md
What scene_set_visibility does on Blender Copilot MCP Server
AI agents use scene_set_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 scene_set_visibility is rated Medium
This tool modifies object visibility settings in Blender, which are reversible state changes to the scene. It is not destructive (visibility can be toggled back), does not delete data, does not execute arbitrary code, and does not involve financial operations. The blast radius is medium because an AI agent could hide critical objects in a scene, disrupting a user's work session, but the action is fully reversible.
From the tool's definition Tool name 'scene_set_visibility' with description 'Set object visibility in viewport and render' indicates modification of scene state properties.
Attacks that exploit this kind of access
The rule that runs scene_set_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 scene_set_visibility, this is the rule to start with:
scene_set_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 scene_set_visibility call is checked against it from then on.
Questions about scene_set_visibility
Set object visibility in viewport and render. 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 scene_set_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.
scene_set_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 scene_set_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 scene_set_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.
scene_set_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