list_scenes

List all scenes in the current Blender file.

SERVERBlender SOURCEsandraschi/blender-mcp

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/sandraschi-blender-mcp/list-scenes.md

WHAT IT DOES

What list_scenes does on Blender

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

RISK

Why list_scenes is rated Low

This tool queries and retrieves information about existing scenes in a Blender file. It has no side effects, does not create, modify, or delete data, and poses minimal security risk. It falls clearly into the Read category.

From the tool's definition Tool description: 'List all scenes in the current Blender file.' The verb 'list' is explicitly read-only and retrieves scene data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_scenes safely

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

list_scenes Allowed

list_scenes 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": {
    "list_scenes": {}
  }
}

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

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

FAQ

Questions about list_scenes

What does the list_scenes tool do? +

List all scenes in the current Blender file. It is categorised as a Read tool in the Blender MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_scenes? +

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

What risk level is list_scenes? +

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

Can I rate-limit list_scenes? +

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

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

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

KEEP EXPLORING

More on Blender, and thousands of servers like it.

This server

All 81 Blender tools →

Across the catalogue

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

Guides

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