multiplayer_test_status

Read the host-side state of the local multiplayer test harness without changing it: play/network state, connection roster, tracked client PIDs and uptime, and join-wait progress. The bridge cannot inspect or drive the separate client windows; use host-side replication inspectors for assertions.

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/multiplayer-test-status.md

WHAT IT DOES

What multiplayer_test_status does on Sbox

AI agents call multiplayer_test_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.

RISK

Why multiplayer_test_status is rated Low

Tool retrieves multiplayer test harness state without modification or side effects.

From the tool's definition Read the host-side state without changing it; play/network state, connection roster.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs multiplayer_test_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 multiplayer_test_status, this is the rule to start with:

multiplayer_test_status Allowed

multiplayer_test_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "multiplayer_test_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every multiplayer_test_status call is checked against it from then on.

FAQ

Questions about multiplayer_test_status

What does the multiplayer_test_status tool do? +

How do I enforce a policy on multiplayer_test_status? +

Register the Sbox MCP server in PolicyLayer and add a rule for multiplayer_test_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.

What risk level is multiplayer_test_status? +

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

Can I rate-limit multiplayer_test_status? +

Yes. Add a rate_limit block to the multiplayer_test_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.

How do I block multiplayer_test_status completely? +

Set action: deny in the PolicyLayer policy for multiplayer_test_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.

What MCP server provides multiplayer_test_status? +

multiplayer_test_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.

KEEP EXPLORING

More on Sbox, and thousands of servers like it.

This server

All 287 Sbox tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →