get_scene_hierarchy
Get the scene tree — GameObjects with their names, GUIDs, components, and parent/child relationships. Pair maxDepth with rootId to drill into a subtree without paying for the whole scene. On a dressed scene (hundreds of objects) pass namesOnly:true first — it returns just {id,name,childCount} per...
This record as markdown: /tools/sbox/get-scene-hierarchy.md
What get_scene_hierarchy does on Sbox
AI agents call get_scene_hierarchy to retrieve information from Sbox without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_scene_hierarchy is rated Low
Retrieves scene structure and metadata without creating, modifying, or deleting game objects or data.
From the tool's definition Get the scene tree, GameObjects with names, GUIDs, components, parent/child relationships.
Attacks that exploit this kind of access
The rule that runs get_scene_hierarchy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_scene_hierarchy, this is the rule to start with:
get_scene_hierarchy 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 Sbox, apply this rule, and every get_scene_hierarchy call is checked against it from then on.
Questions about get_scene_hierarchy
Get the scene tree — GameObjects with their names, GUIDs, components, and parent/child relationships. Pair maxDepth with rootId to drill into a subtree without paying for the whole scene. On a dressed scene (hundreds of objects) pass namesOnly:true first — it returns just {id,name,childCount} per object (no components/enabled) for a lighter. It is categorised as a Read tool in the Sbox MCP Server, which means it retrieves data without modifying state.
Register the Sbox MCP server in PolicyLayer and add a rule for get_scene_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 Sbox. Nothing to install.
get_scene_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 get_scene_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 get_scene_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.
get_scene_hierarchy is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue