blender.setup_lighting

Create or update scene lighting

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/blender.setup-lighting.md

WHAT IT DOES

What blender.setup_lighting does on CoWork OS

AI agents use blender.setup_lighting to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.

RISK

Why blender.setup_lighting is rated Medium

The tool creates or modifies lighting in a Blender scene. This is a reversible write operation — it sets or updates scene properties but does not delete data, execute arbitrary code, or involve financial transactions. Misuse could alter a scene's lighting unexpectedly, but effects are reversible.

From the tool's definition Create or update scene lighting

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blender.setup_lighting safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender.setup_lighting, this is the rule to start with:

blender.setup_lighting Rate-limited

blender.setup_lighting 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "blender.setup_lighting": {
      "limits": [
        {
          "counter": "blender.setup_lighting_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every blender.setup_lighting call is checked against it from then on.

FAQ

Questions about blender.setup_lighting

What does the blender.setup_lighting tool do? +

Create or update scene lighting. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on blender.setup_lighting? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for blender.setup_lighting: 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 CoWork OS. Nothing to install.

What risk level is blender.setup_lighting? +

blender.setup_lighting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit blender.setup_lighting? +

Yes. Add a rate_limit block to the blender.setup_lighting 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.

How do I block blender.setup_lighting completely? +

Set action: deny in the PolicyLayer policy for blender.setup_lighting. 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.

What MCP server provides blender.setup_lighting? +

blender.setup_lighting is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →