find_objects
Query the scene for GameObjects by name (case-insensitive substring), component type name, and/or tag — combine filters (AND). Returns { count, total, showing, truncated, objects:[{id,name}] } — total is EVERY match in the scene, showing/count how many rows were returned (limit default 50, max 50...
This record as markdown: /tools/sbox/find-objects.md
What find_objects does on Sbox
AI agents call find_objects 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 find_objects is rated Low
Retrieves game object metadata without side effects; supports game development workflow inspection.
From the tool's definition Query the scene for GameObjects by name, component type, tag — Read-only
Attacks that exploit this kind of access
The rule that runs find_objects 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 find_objects, this is the rule to start with:
find_objects 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 find_objects call is checked against it from then on.
Questions about find_objects
Query the scene for GameObjects by name (case-insensitive substring), component type name, and/or tag — combine filters (AND). Returns { count, total, showing, truncated, objects:[{id,name}] } — total is EVERY match in the scene, showing/count how many rows were returned (limit default 50, max 500), truncated:true when rows were cut so you can raise limit or narrow the filter. Read-only; works during play. Use it to get GUIDs to feed into align/distribute/set_tint/group/delete/etc. 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 find_objects: 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.
find_objects 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 find_objects 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 find_objects. 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.
find_objects 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