network_spawn
Network-enable a GameObject so it is synchronized across all connected clients. Calls NetworkSpawn()
This record as markdown: /tools/sbox/network-spawn.md
What network_spawn does on Sbox
AI agents invoke network_spawn 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 network_spawn is rated High
This tool triggers an external operation (NetworkSpawn()) that propagates a game object's state across all connected clients in a multiplayer environment. It is not a simple data write — it executes a networked synchronization action with real-time effects on all connected players, making misuse potentially high-impact (e.g., spawning unintended objects for all clients simultaneously).
From the tool's definition 'Network-enable a GameObject so it is synchronized across all connected clients. Calls NetworkSpawn()'
Attacks that exploit this kind of access
The rule that runs network_spawn 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 network_spawn, this is the rule to start with:
network_spawn 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 network_spawn call is checked against it from then on.
Questions about network_spawn
Network-enable a GameObject so it is synchronized across all connected clients. Calls NetworkSpawn(). 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 network_spawn: 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.
network_spawn 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 network_spawn 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 network_spawn. 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.
network_spawn 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