light_setup_studio
Set up studio lighting with softboxes (4 area lights + white world).
This record as markdown: /tools/dwgx-blender-copilot/light-setup-studio.md
What light_setup_studio does on Blender Copilot MCP Server
AI agents use light_setup_studio 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 light_setup_studio is rated Medium
This tool creates and configures lighting objects in a Blender scene (adds 4 area lights and sets up world lighting). It is a Write operation as it creates new objects and modifies scene settings, but the effects are reversible within Blender. Misuse could unintentionally overwrite existing lighting setups, giving it medium severity.
From the tool's definition Set up studio lighting with softboxes (4 area lights + white world)
Attacks that exploit this kind of access
The rule that runs light_setup_studio 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 light_setup_studio, this is the rule to start with:
light_setup_studio 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 light_setup_studio call is checked against it from then on.
Questions about light_setup_studio
Set up studio lighting with softboxes (4 area lights + white world). 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 light_setup_studio: 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.
light_setup_studio 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 light_setup_studio 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 light_setup_studio. 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.
light_setup_studio 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