New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

runtime_seed_rng

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

SERVERBreakpoint SOURCEbreakpoint-mcp
Medium RISK CLASS
Category Write
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 runtime_seed_rng does on Breakpoint

AI agents use runtime_seed_rng to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.

ParameterTypeRequiredDescription
peer string — Headless peer id from runtime_spawn_peers; omit for the default running game.
seed integer Yes Seed value for the global RNG
confirm boolean — Skip the confirmation prompt (auto-approve)

Parameters from the server's own tool schema.

Why runtime_seed_rng is rated Medium

An AI agent can call runtime_seed_rng faster than any human can review: one bad instruction and it creates or modifies resources in Breakpoint by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

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 Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

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 Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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.

More on Breakpoint, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Breakpoint's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.