MCP Path

OPEN_NAVIGATION action category

OPEN_NAVIGATION action category 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.

Catalog path

Reference page for a documented MCP capability path.

Type: MCP path
Family: Surface Explorer (High Risk, Opt-in)
Effect: changes state
Status: Reference
Path: 28.13

Purpose

What this entry explains

What it does

This reference explains OPEN_NAVIGATION action category 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 carry out the bounded step "OPEN_NAVIGATION action category" 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.

Signal, gate, behavior, boundary

OPEN_NAVIGATION action category 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.

When agents cite it

An agent cites this path when it needs OPEN_NAVIGATION action category as context for a decision, block, target check, or follow-up tool choice.

Why no callable name

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.

Signals and rule

Relevant response signals: actionClass. Safety axes: 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.

nova.explore_surface nova.tools_bundle Safety-Gate-Block

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
`actionClass`	Response field named by the catalog source. Treat it as current evidence for the next decision.

Safety

Boundary before execution

Effect

Can change browser, page, or workflow state. The target and expected result must be clear before execution.

Agent rule

Confirm the current target first, perform only the intended bounded action, and verify the resulting page or workflow state afterwards.

Human control

For humans, this entry names the browser or workflow state in risk-bounded actions with visible user control that may change, so the action can be reviewed before and after execution.

High-Impact Review

Execution boundary and recheck hints

Review category: Auto-apply/mutating flows

Execution boundary

Mutating steps may run only with confirmed target, expected effect, user control, and result check.

Typical false assumption

False assumption: a guard or auto-apply signal replaces current target and result checks.

Visible user control

The user must be able to review action, target, approval, block signal, and visible result.

Agent rule

Execute only the intended step, then verify state and stop on warning, block, or target change.

Abort or recheck

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.

Browser state 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 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 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.