runtime_assert_node_state
Assert that properties of a LIVE node equal expected values (read-only verification). Reports per-property mismatches; supports an optional absolute numeric tolerance.
This record as markdown: /tools/breakpoint-mcp/runtime-assert-node-state.md
What runtime_assert_node_state does on Breakpoint
AI agents call runtime_assert_node_state to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Node path (relative to the current scene; '/root/...' absolute allowed) |
peer | string | — | Target a headless peer by id (from runtime_spawn_peers). Omit to address the default running game. |
expect | object | Yes | Map of property name -> expected value (JSON; use the tagged-Variant form for complex types like Vector2/Color) |
tolerance | number | — | Absolute tolerance for numeric comparisons (default 0 = exact match) |
Parameters from the server's own tool schema.
Why runtime_assert_node_state is rated Low
This is a verification/assertion tool that retrieves and compares node properties against expected values. It has no side effects, performs no modifications, and only performs validation checks. This fits squarely within the Read category as it queries data and reports results without changing state.
From the tool's definition Tool description explicitly states 'read-only verification' and 'Assert that properties...equal expected values'. The tool only checks/verifies node state without modifying it.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs runtime_assert_node_state 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_assert_node_state, this is the rule to start with:
runtime_assert_node_state is read-only, so it stays allowed. 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_assert_node_state call is checked against it from then on.
Questions about runtime_assert_node_state
Assert that properties of a LIVE node equal expected values (read-only verification). Reports per-property mismatches; supports an optional absolute numeric tolerance. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
runtime_assert_node_state accepts 4 parameters: path, peer, expect, tolerance. Required: path, expect. 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_assert_node_state: 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_assert_node_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the runtime_assert_node_state 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_assert_node_state. 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_assert_node_state 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.
This server
Across the catalogue