This record as markdown: /tools/sbox/playtest.md
What playtest does on Sbox
AI agents invoke playtest 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 playtest is rated High
The tool name 'playtest' strongly implies launching or running a game session within the s&box engine, which constitutes executing an external operation (running the game). This falls under Execute. Severity is high because triggering a playtesting session could launch processes, consume resources, or interact with the game runtime in unpredictable ways.
From the tool's definition Tool name 'playtest' on an MCP server for the s&box game engine that 'enables Claude to build games through conversation'
Attacks that exploit this kind of access
The rule that runs playtest 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 playtest, this is the rule to start with:
playtest 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 playtest call is checked against it from then on.
Questions about playtest
playtest is a execute tool on the Sbox MCP server. 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 playtest: 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.
playtest 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 playtest 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 playtest. 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.
playtest 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