MCP Path
Read-Navigation Klasse
Read-Navigation Klasse is a public reference for risk-bounded actions with visible user control. 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
- Surface Explorer (High Risk, Opt-in)
- Effect
- read-only
- Status
- Reference
- Path
- 28.9
Purpose
What this entry explains
What it does
This reference explains Read-Navigation Klasse for risk-bounded actions with visible user control. 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 "Read-Navigation Klasse" for risk-bounded actions with visible user control.
- 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.
Read-Navigation Klasse describes a gate for risk-bounded actions with visible user control. 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 Read-Navigation Klasse 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: readNavClass, PAGINATION_LINK, LOAD_MORE_BUTTON, actionClass and further signals. Safety axes: Read current state, Browser state, Automation, User confirmation. 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 prepares a bounded run in risk-bounded actions with visible user control and must keep scope, progress, and stop condition visible.
The agent starts with nova.explore_surface, reads the current response or reference, and only then chooses the concrete next tool.
Scope, budget, progress, stop condition, and terminal status remain part of the run.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 |
|---|---|
readNavClass | Response field named by the catalog source. Treat it as current evidence for the next decision. |
PAGINATION_LINK | Response field named by the catalog source. Treat it as current evidence for the next decision. |
LOAD_MORE_BUTTON | Response field named by the catalog source. Treat it as current evidence for the next decision. |
actionClass | Response field named by the catalog source. Treat it as current evidence for the next decision. |
safetyDecision | Decision or block signal. It explains why the current step should continue, pause, or stop. |
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 risk-bounded actions with visible user control and which current signal should be checked before trusting the result.
High-Impact Review
Execution boundary and recheck hints
Review category: Auto-apply/mutating flows
Mutating steps may run only with confirmed target, expected effect, user control, and result check.
False assumption: a guard or auto-apply signal replaces current target and result checks.
The user must be able to review action, target, approval, block signal, and visible result.
Execute only the intended step, then verify state and stop on warning, block, or target change.
Recheck if candidate budget, gate, visible state, or expected effect do not line up.
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.automation_run
Starts or monitors crawls, sequences, schedulers, tasks, batches, or longer runs.
Keep scope, budget, progress, stop condition, and terminal status visible before and during the run.user_confirmation
Requires visible confirmation, target review, approval, or deliberate user control.
Do not proceed until the required confirmation is visible or unambiguous in the current context.