New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

inspect_networked_object

Inspect the live networking contract of a GameObject. Returns {id, name, network: {active, isProxy, isOwner, isCreator, ownerId, ownerSteamId, ownerTransfer, orphaned, flags}, components: [{component, fields: [{name, type, isSync, syncFlags, value}]}]} — by default only [Sync]-marked fields are l...

SERVERSbox SOURCEsbox-mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Retrieves networking state and component data without modifying game objects or network state.

From the tool's definition Inspect live networking contract, returns object status and component fields, read-only query.

Questions about inspect_networked_object

What does the inspect_networked_object tool do? +

Inspect the live networking contract of a GameObject. Returns {id, name, network: {active, isProxy, isOwner, isCreator, ownerId, ownerSteamId, ownerTransfer, orphaned, flags}, components: [{component, fields: [{name, type, isSync, syncFlags, value}]}]} — by default only [Sync]-marked fields are listed (components with none are omitted). Unlike get_network_status (session-only), this is per-object — the way to verify a host-authoritative or ownership change actually replicated; works in edit or play mode. Follow up with set_ownership to change the owner, or networking_lint to find the code-level cause of a bad [Sync] value. It is categorised as a Read tool in the Sbox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on inspect_networked_object? +

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.

What risk level is inspect_networked_object? +

inspect_networked_object is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit inspect_networked_object? +

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.

How do I block inspect_networked_object completely? +

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.

What MCP server provides inspect_networked_object? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sbox's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.