Get detailed information about the current Blender scene
AI agents call get_scene_info to retrieve information from BlenderMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about an existing Blender scene. It performs no modifications, deletions, code execution, or financial operations. It is a straightforward read/query operation with minimal blast radius if misused by an AI agent, as it only exposes scene information that is already accessible within Blender.
From the tool's definition Tool name 'get_scene_info' and description 'Get detailed information about the current Blender scene' indicate a query operation that retrieves scene metadata without modifying state.
Documented attack patterns abuse exactly the kind of access get_scene_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BlenderMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_scene_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_scene_info": {}
}
}get_scene_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about the current Blender scene. It is categorised as a Read tool in the BlenderMCP MCP Server, which means it retrieves data without modifying state.
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.
get_scene_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
get_scene_info is provided by the Blender MCP server (nanashi1526/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BlenderMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 BlenderMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.