analyze_scene
Analyze the entire scene for statistics and potential issues.
This record as markdown: /tools/dwgx-blender-copilot/analyze-scene.md
What analyze_scene does on Blender Copilot MCP Server
AI agents call analyze_scene 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.
Why analyze_scene is rated Low
This tool retrieves and reports information about the scene state (statistics, potential issues) without creating, modifying, deleting, or executing code/commands. It is a non-destructive read operation with minimal risk; misuse would only surface unwanted information rather than cause harm to assets or external systems.
From the tool's definition analyze_scene: Analyze the entire scene for statistics and potential issues. The verb 'analyze' and the stated purpose of gathering 'statistics' and identifying 'issues' indicate inspection/querying of existing scene data without modification or execution of…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs analyze_scene 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 analyze_scene, this is the rule to start with:
analyze_scene is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every analyze_scene call is checked against it from then on.
Questions about analyze_scene
Analyze the entire scene for statistics and potential issues. It is categorised as a Read tool in the Blender Copilot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for analyze_scene: 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.
analyze_scene 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 analyze_scene 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 analyze_scene. 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.
analyze_scene 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.
More on Blender Copilot MCP Server, and thousands of servers like it.
This server
Across the catalogue