This record as markdown: /tools/sbox/set-time-scale.md
What set_time_scale does on Sbox
AI agents invoke set_time_scale 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 set_time_scale is rated High
This tool appears to modify the time scale of a running game simulation, which is an operation that affects the execution state of the game engine. It doesn't permanently delete data or move money, but it does manipulate a live running process. The description is truncated/incomplete ('Set the running game'), which reduces confidence. Severity is medium as misuse could disrupt gameplay but is likely reversible.
From the tool's definition 'Set the running game' — implies modifying the time scale of an actively running game simulation
Attacks that exploit this kind of access
The rule that runs set_time_scale 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 set_time_scale, this is the rule to start with:
set_time_scale 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 set_time_scale call is checked against it from then on.
Questions about set_time_scale
Set the running game. 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 set_time_scale: 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.
set_time_scale 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 set_time_scale 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 set_time_scale. 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.
set_time_scale 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