runtime_peers_digest
Compare runtime_state_digest across two or more peers over the SAME root and field set (read-only): converged when every peer's digest is byte-equal, otherwise diverged_at names the node paths that disagree. The sequence that converges: runtime_spawn_peers, then per peer runtime_time_scale{scale:...
This record as markdown: /tools/breakpoint-mcp/runtime-peers-digest.md
What runtime_peers_digest does on Breakpoint
AI agents invoke runtime_peers_digest 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 |
|---|---|---|---|
root | string | Yes | Root node path to digest in each peer (same path on every peer) |
peers | array | — | Peer ids to compare (default: every live peer; at least two are required) |
fields | array | — | Property names to capture per node (default: the runtime_state_digest defaults) |
max_depth | integer | — | Max recursion depth (default 8) |
Parameters from the server's own tool schema.
Why runtime_peers_digest is rated High
runtime_peers_digest triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs runtime_peers_digest 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_peers_digest, this is the rule to start with:
runtime_peers_digest 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_peers_digest call is checked against it from then on.
Questions about runtime_peers_digest
Compare runtime_state_digest across two or more peers over the SAME root and field set (read-only): converged when every peer's digest is byte-equal, otherwise diverged_at names the node paths that disagree. The sequence that converges: runtime_spawn_peers, then per peer runtime_time_scale{scale:0} to FREEZE FIRST, runtime_set_property{peer} to equalise the starting state, runtime_seed_rng{seed} with one seed, runtime_step_frames{frames:K,kind:"physics"}, then this. FOUR PRECONDITIONS, measured on Godot 4.3 (convergence re-measured on 4.7); skip any one and the peers diverge. (1) Step the fixed physics timestep, kind:"physics": idle-frame delta is each process's own wall-clock time and never converges. (2) Draw from the global RNG only on frames you step: runtime_seed_rng seeds one stream shared by the whole project, and freezing does not stop it being drawn (time_scale 0 zeroes delta but callbacks still fire), so unguarded draws burn it while frozen and idle-frame draws burn it during the step. Guard draws on delta > 0 and give idle-frame code its own RandomNumberGenerator. (3) Peers free-run for different times before the freeze, so freeze first, then equalise with runtime_set_property{peer}. (4) Same machine only: nothing is claimed across machines. 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_peers_digest accepts 4 parameters: root, peers, fields, max_depth. Required: root. 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_peers_digest: 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_peers_digest 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_peers_digest 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_peers_digest. 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_peers_digest 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