runtime_time_scale
Set Engine.time_scale on the running game: 0 freezes time, 1 is normal, >1 fast, <1 slow-motion. DESTRUCTIVE (alters the running game's clock) — gated by confirmation. Freeze with scale 0, then runtime_step_frames to advance deterministically before asserting.
This record as markdown: /tools/breakpoint-mcp/runtime-time-scale.md
What runtime_time_scale does on Breakpoint
AI agents invoke runtime_time_scale to trigger actions in Breakpoint. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
peer | string | — | Target a headless peer by id (from runtime_spawn_peers). Omit to address the default running game. |
scale | number | Yes | 0 = freeze, 1 = normal, N = slow/fast (negative is clamped to 0) |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
Parameters from the server's own tool schema.
Why runtime_time_scale is rated High
This tool triggers external operations (modifying game engine time scale) whose effects depend on the numeric argument provided. While marked 'DESTRUCTIVE' in the description, it does not irreversibly delete or overwrite data; instead, it executes a state-altering command on a running process. The effect is reversible (time scale can be reset), so it maps to Execute rather than Destructive.
From the tool's definition 'Set Engine.time_scale on the running game' and 'alters the running game's clock' — modifies runtime state of a live game engine.
Attacks that exploit this kind of access
The rule that runs runtime_time_scale safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runtime_time_scale, this is the rule to start with:
runtime_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 Breakpoint, apply this rule, and every runtime_time_scale call is checked against it from then on.
Questions about runtime_time_scale
Set Engine.time_scale on the running game: 0 freezes time, 1 is normal, >1 fast, <1 slow-motion. DESTRUCTIVE (alters the running game's clock) — gated by confirmation. Freeze with scale 0, then runtime_step_frames to advance deterministically before asserting. It is categorised as a Execute tool in the Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
runtime_time_scale accepts 3 parameters: peer, scale, confirm. Required: scale. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for runtime_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 Breakpoint. Nothing to install.
runtime_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 runtime_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 runtime_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.
runtime_time_scale is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
Across the catalogue