physics_overlap
Spatial volume query: return the GameObjects whose colliders intersect a SPHERE (center + radius) or a BOX (center + size) — the volume counterpart to raycast
This record as markdown: /tools/sbox/physics-overlap.md
What physics_overlap does on Sbox
AI agents call physics_overlap 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 physics_overlap is rated Low
physics_overlap performs a passive spatial lookup to identify which game objects exist within a defined volume. It has no side effects, creates no objects, executes no code, and does not modify game state. This is a classic read operation analogous to raycasting for collision detection purposes.
From the tool's definition Tool description states 'Spatial volume query: return the GameObjects' — explicitly a query operation that retrieves data about colliders in a specified volume without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs physics_overlap 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 physics_overlap, this is the rule to start with:
physics_overlap 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 physics_overlap call is checked against it from then on.
Questions about physics_overlap
Spatial volume query: return the GameObjects whose colliders intersect a SPHERE (center + radius) or a BOX (center + size) — the volume counterpart to raycast. 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 physics_overlap: 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.
physics_overlap 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 physics_overlap 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 physics_overlap. 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.
physics_overlap 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