MCP Path
Claim + Navigation + Release
Claim + Navigation + Release is a public reference for edge cases, product boundaries, and robust failure paths. 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
- Cross-Feature Integration
- Effect
- changes state
- Status
- Reference
- Path
- 50.5
Purpose
What this entry explains
What it does
This reference explains Claim + Navigation + Release for edge cases, product boundaries, and robust failure paths. 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 "Claim + Navigation + Release" for edge cases, product boundaries, and robust failure paths.
- 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.
Claim + Navigation + Release describes a gate for edge cases, product boundaries, and robust failure paths. 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 Claim + Navigation + Release 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: current discovery and actual response status. Safety axes: Browser state, External, 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
A task in edge cases, product boundaries, and robust failure paths can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with Crawl -> Learn Loop, reads the current response or reference, and only then chooses the concrete next tool.
Current discovery, target, user control, warning signals, and result check come before execution.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 fields
No fixed public response field is derived from the catalog source for this path. Use current tool discovery and the actual response before chaining the next step.
Safety
Boundary before execution
Can change browser, page, or workflow state. The target and expected result must be clear before execution.
Confirm the current target first, perform only the intended bounded action, and verify the resulting page or workflow state afterwards.
For humans, this entry names the browser or workflow state in edge cases, product boundaries, and robust failure paths that may change, so the action can be reviewed before and after execution.
High-Impact Review
Execution boundary and recheck hints
Review category: Proxy/external connection
External targets, proxies, gateways, and transport paths may be used only with checked target, status, and approval.
False assumption: a reachable external tool is automatically part of the allowed Nova tool chain.
Target, transport status, import or connection approval, and expected data movement must be visible.
Do not silently add third-party tools; check current approval, target, and response status before use.
Recheck if the gateway, proxy, remote source, or target system changes or emits warnings.
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_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.external_connection
Uses proxy, external MCP gateways, network routes, third-party integrations, or import paths.
Check external target, transport status, and approval before use; do not silently chain third-party tools.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.