Get the full scene hierarchy as a JSON-formatted string.
AI agents call scene_get_hierarchy to retrieve information from Blender without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the hierarchical structure of a Blender scene without creating, modifying, deleting, or executing any operations. It returns read-only information in JSON format, fitting the 'Read' category pattern of safe data access.
From the tool's definition Tool name 'scene_get_hierarchy' with description 'Get the full scene hierarchy as a JSON-formatted string' indicates pure data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access scene_get_hierarchy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Blender, and nothing reaches the server without passing your rules. This is the rule we recommend for scene_get_hierarchy:
{
"version": "1",
"default": "deny",
"tools": {
"scene_get_hierarchy": {}
}
}scene_get_hierarchy 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 the full scene hierarchy as a JSON-formatted string. It is categorised as a Read tool in the Blender MCP Server, which means it retrieves data without modifying state.
Register the Blender MCP server in PolicyLayer and add a rule for scene_get_hierarchy: 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.
scene_get_hierarchy 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 scene_get_hierarchy 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 scene_get_hierarchy. 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.
scene_get_hierarchy 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.
Start from Blender, 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.
77 Blender tools catalogued and risk-classified — across an index of 43,000+ MCP servers.