get_bounds
Get provenance-rich world bounds for a GameObject. Preserves legacy top-level center/size/extents/mins/maxs/radius/position/empty for compatibility, and adds render plus independent physics and solidPhysics aggregates. Collider outputs include trigger policy, capped contributor GameObject IDs and...
This record as markdown: /tools/sbox/get-bounds.md
What get_bounds does on Sbox
AI agents call get_bounds 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_bounds is rated Low
Retrieves game object bounds data without modifying state or executing code.
From the tool's definition Get world bounds for GameObject; read-only and play-aware.
Attacks that exploit this kind of access
The rule that runs get_bounds 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_bounds, this is the rule to start with:
get_bounds 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_bounds call is checked against it from then on.
Questions about get_bounds
Get provenance-rich world bounds for a GameObject. Preserves legacy top-level center/size/extents/mins/maxs/radius/position/empty for compatibility, and adds render plus independent physics and solidPhysics aggregates. Collider outputs include trigger policy, capped contributor GameObject IDs and component type names, unsupported counts, and the exact API source. Read-only and play-aware. 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_bounds: 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_bounds 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_bounds 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_bounds. 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_bounds 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