inspect_networked_object
Inspect the live networking contract of a GameObject: Network.Owner/IsProxy/IsOwner/Active, OwnerTransfer + OrphanedMode, and every component
This record as markdown: /tools/sbox/inspect-networked-object.md
What inspect_networked_object does on Sbox
AI agents call inspect_networked_object 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 inspect_networked_object is rated Low
The tool reads and queries the state of a networked game object (checking Network properties like Owner, IsProxy, IsOwner, Active, OwnerTransfer, OrphanedMode, and component data). No side effects, modifications, or external operations are indicated. This is a pure Read operation with minimal blast radius — useful for debugging but no ability to alter game state.
From the tool's definition Tool name and description use 'inspect' and 'every component' — retrieves live networking state and properties of a GameObject with no modification capability described
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs inspect_networked_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 inspect_networked_object, this is the rule to start with:
inspect_networked_object 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 inspect_networked_object call is checked against it from then on.
Questions about inspect_networked_object
Inspect the live networking contract of a GameObject: Network.Owner/IsProxy/IsOwner/Active, OwnerTransfer + OrphanedMode, and every component. 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 inspect_networked_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.
inspect_networked_object 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 inspect_networked_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 inspect_networked_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.
inspect_networked_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