runtime_seed_rng

SERVERBreakpoint SOURCEbreakpoint-mcp

High RISK CLASS

Category Execute

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/runtime-seed-rng.md

WHAT IT DOES

What runtime_seed_rng does on Breakpoint

AI agents invoke runtime_seed_rng 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.
`seed`	integer	Yes	Seed value for the global RNG
`confirm`	boolean	—	Auto-approve this destructive action (skip the confirmation prompt)

Parameters from the server's own tool schema.

RISK

Why runtime_seed_rng is rated High

This tool modifies the global RNG state of a running game process, which is an external runtime operation with side effects. While described as 'DESTRUCTIVE' in the description, it doesn't irreversibly delete or overwrite data — it changes runtime state in a way that can be re-seeded.

From the tool's definition Seed the running game's GLOBAL random number generator (GDScript seed()) so a playtest is reproducible. DESTRUCTIVE (changes RNG state) — gated by confirmation.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

runtime_seed_rng Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "runtime_seed_rng": {
      "limits": [
        {
          "counter": "runtime_seed_rng_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about runtime_seed_rng

What does the runtime_seed_rng tool do? +

Seed the running game's GLOBAL random number generator (GDScript seed()) so a playtest is reproducible. DESTRUCTIVE (changes RNG state) — gated by confirmation. Seeds only the global RNG (randi/randf), not per-instance RandomNumberGenerators or physics determinism. IMPORTANT when comparing peers: this is ONE stream shared by every caller in the project, and FREEZING DOES NOT STOP IT BEING CONSUMED — time_scale 0 makes delta 0 but _process/_physics_process still fire, so code that draws unconditionally burns draws at wall-clock rate even while frozen, including in the gap between this call and runtime_step_frames. For peers to converge the global stream must be consumed ONLY on frames you are actually stepping: guard draws on delta > 0, and give idle-frame code its own RandomNumberGenerator. Measured on real Godot 4.3 — with both, three peers converge byte-equal even with a deliberate stagger between each peer's seed and step; with either violated, they diverge every time. 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.

What parameters does runtime_seed_rng accept? +

runtime_seed_rng accepts 3 parameters: peer, seed, confirm. Required: seed. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on runtime_seed_rng? +

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

What risk level is runtime_seed_rng? +

runtime_seed_rng is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit runtime_seed_rng? +

Yes. Add a rate_limit block to the runtime_seed_rng 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 runtime_seed_rng completely? +

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

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

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →