get_scene_info

Get information about the current Blender scene including all objects, frame range, and render settings

SERVERBlenderMCP SOURCEaryeon0228/blendermcp

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/aryeon0228-blendermcp/get-scene-info.md

WHAT IT DOES

What get_scene_info does on BlenderMCP

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

RISK

Why get_scene_info is rated Low

This tool only retrieves metadata about the Blender scene state (objects, frame range, render settings) without creating, modifying, deleting, executing code, or performing any side effects. It is a straightforward information retrieval operation with minimal risk if misused by an AI agent.

From the tool's definition The tool description explicitly states it 'Get[s] information about the current Blender scene' - a retrieval operation with no modification capability. The verb 'get' combined with 'information about' clearly indicates a read-only query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_scene_info safely

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

get_scene_info Allowed

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

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

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

FAQ

Questions about get_scene_info

What does the get_scene_info tool do? +

Get information about the current Blender scene including all objects, frame range, and render settings. It is categorised as a Read tool in the BlenderMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_scene_info? +

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

What risk level is get_scene_info? +

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

Can I rate-limit get_scene_info? +

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

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

get_scene_info is provided by the Blender MCP server (aryeon0228/blendermcp). 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 12 Blender tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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