MCP Path
History No-op & Validation
History No-op & Validation is a public reference for navigation, history, and controlled page changes. It names the signal, policy, or flow an agent should understand before choosing a concrete tool.
Reference page for a documented MCP capability path.
- Type
- MCP path
- Family
- Navigation & SPA Routing
- Effect
- read-only
- Status
- Reference
- Path
- 3.14
Purpose
What this entry explains
What it does
This reference explains History No-op & Validation for navigation, history, and controlled page changes. It is kept as a named reference so agents can cite the flow without inventing a tool name.
Use when
- Use this entry when an agent needs to check the state or evidence for "History No-op & Validation" for navigation, history, and controlled page changes.
- Use it as a reference path when the catalog describes a capability but no single public tool name is explicit.
- Use it before chaining follow-up tools so the next step is based on current evidence.
Reference Use
How agents should cite and apply this area
Examples are maintained at family level and use only public tool names or reference paths already present in the catalog.
History No-op & Validation describes a signal for navigation, history, and controlled page changes. The path shows which signal, gate, behavior, or boundary must be checked before choosing a concrete tool.
An agent cites this path when it needs History No-op & Validation as context for a decision, block, target check, or follow-up tool choice.
The public source does not name one callable tool for this path. The documentation therefore keeps it as a reference path and does not invent a callable name.
Relevant response signals: entryId, offset, reasonCode, navigation.history_already_current. Safety axes: Read current state, Browser state. The reference path alone is not permission to execute. Before acting, check current MCP discovery, visible target, scope, and the actual response.
Family example
An agent needs to change visible state in navigation, history, and controlled page changes without guessing target or result from an earlier session.
The agent starts with nova.navigate, reads the current response or reference, and only then chooses the concrete next tool.
Change only the confirmed target, then check visible state and stop on mismatch.Contract
Inputs and important response fields
This page is a public reference. Agents and integrators should still read current MCP tool discovery before execution, because schemas can be gated by settings or version.
Inputs
No stable public input field is derived from the catalog source for this path. Read current MCP discovery before execution.
| Response field | Explanation |
|---|---|
entryId | Identifier or reference value. Do not guess it from memory; read it from the current response. |
offset | Paging or size signal for long result sets. It indicates whether more data needs a follow-up request. |
reasonCode | Machine-readable reason for a warning, block, or special behavior. |
navigation.history_already_current | Response field named by the catalog source. Treat it as current evidence for the next decision. |
Safety
Boundary before execution
Reads current state or evidence. It should not be treated as permission to act without a fresh next-step check.
Use the response as current evidence, then choose a more specific next tool only after target, scope, and freshness are clear.
For humans, this entry explains what an agent reads in navigation, history, and controlled page changes and which current signal should be checked before trusting the result.
Safety Axes
How this path can affect work
Axes are stable catalog signals for humans, agents, and LLM discovery. One path can carry several axes.
read_current_state
Reads current state, response signals, or evidence without treating that alone as permission for a follow-up action.
Use the signal as current evidence and re-check target, scope, and visible state before any follow-up action.browser_state_change
Changes tab, navigation, focus, claim, scroll position, window state, or browser environment.
Confirm the target context visibly before execution and verify that the expected browser state was reached afterwards.