light_list

List all lights in the scene with their properties.

SERVERBlender Copilot MCP Server SOURCEdwgx/blender-copilot

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dwgx-blender-copilot/light-list.md

WHAT IT DOES

What light_list does on Blender Copilot MCP Server

AI agents call light_list to retrieve information from Blender Copilot MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why light_list is rated Low

This tool retrieves and displays information about existing lights in a Blender scene. It performs no modifications, deletions, code execution, or financial operations. It is a straightforward read operation with no side effects, placing it firmly in the Read category with low severity since the blast radius of misuse is minimal—an agent can only view existing light data.

From the tool's definition Tool name 'light_list' and description 'List all lights in the scene with their properties' indicate a query/retrieval operation with no modification or execution of external commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs light_list 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_list, this is the rule to start with:

light_list Allowed

light_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "light_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every light_list call is checked against it from then on.

FAQ

Questions about light_list

What does the light_list tool do? +

List all lights in the scene with their properties. It is categorised as a Read tool in the Blender Copilot MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on light_list? +

Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for light_list: 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.

What risk level is light_list? +

light_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit light_list? +

Yes. Add a rate_limit block to the light_list 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 light_list completely? +

Set action: deny in the PolicyLayer policy for light_list. 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 light_list? +

light_list 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.

KEEP EXPLORING

More on Blender Copilot MCP Server, and thousands of servers like it.

This server

All 307 Blender Copilot MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →