get_network_status
Check the current multiplayer status: connection state, player count, lobby info, networked objects
This record as markdown: /tools/sbox/get-network-status.md
What get_network_status does on Sbox
AI agents call get_network_status 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 get_network_status is rated Low
This tool retrieves information about network and multiplayer state without creating, modifying, executing commands, or deleting data. It is a passive information query, making it a Read operation with low severity since misuse would only expose game state metadata rather than enable harmful actions.
From the tool's definition Tool name 'get_network_status' and description 'Check the current multiplayer status: connection state, player count, lobby info, networked objects' indicate read-only queries of game state with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs get_network_status 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 get_network_status, this is the rule to start with:
get_network_status 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 get_network_status call is checked against it from then on.
Questions about get_network_status
Check the current multiplayer status: connection state, player count, lobby info, networked objects. 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 get_network_status: 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.
get_network_status 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 get_network_status 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 get_network_status. 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.
get_network_status 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