stop_multiplayer_test
Stop every client process launched by start_multiplayer_test; exited clients are cleared while failed live kills remain tracked for retry. Optionally disconnect the host lobby. alsoStrays is an explicit recovery switch that kills every sbox.exe game client, including clients not launched by this ...
This record as markdown: /tools/sbox/stop-multiplayer-test.md
What stop_multiplayer_test does on Sbox
AI agents invoke stop_multiplayer_test 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 stop_multiplayer_test is rated High
Terminates running game processes and network connections; effects depend on game state and cannot be partially undone.
From the tool's definition Stop every client process, kills sbox.exe game clients, disconnect host lobby.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs stop_multiplayer_test 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 stop_multiplayer_test, this is the rule to start with:
stop_multiplayer_test 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 stop_multiplayer_test call is checked against it from then on.
Questions about stop_multiplayer_test
Stop every client process launched by start_multiplayer_test; exited clients are cleared while failed live kills remain tracked for retry. Optionally disconnect the host lobby. alsoStrays is an explicit recovery switch that kills every sbox.exe game client, including clients not launched by this harness; it never targets the sbox-dev editor process. Returns truthful stopped/remainingPids, per-process cleanup results, and disconnect status. 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 stop_multiplayer_test: 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.
stop_multiplayer_test 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 stop_multiplayer_test 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 stop_multiplayer_test. 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.
stop_multiplayer_test 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