focus_object
Move the editor camera to focus on a specific GameObject (like double-clicking in the hierarchy)
This record as markdown: /tools/sbox/focus-object.md
What focus_object does on Sbox
AI agents invoke focus_object to trigger actions in Sbox. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why focus_object is rated High
This tool triggers an external operation in the s&box editor — moving the editor camera. It doesn't read data, write/modify game data, or destroy anything; it executes a UI/viewport action. Blast radius is very low since it only affects the editor view state.
From the tool's definition Move the editor camera to focus on a specific GameObject (like double-clicking in the hierarchy)
Attacks that exploit this kind of access
The rule that runs focus_object 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 focus_object, this is the rule to start with:
focus_object stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 focus_object call is checked against it from then on.
Questions about focus_object
Move the editor camera to focus on a specific GameObject (like double-clicking in the hierarchy). It is categorised as a Execute tool in the Sbox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sbox MCP server in PolicyLayer and add a rule for focus_object: 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.
focus_object is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the focus_object 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 focus_object. 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.
focus_object 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