MCP Path
Release Token Override
Release Token Override is a public reference for tabs, active targets, and claim state. 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
- Tab Management & Claims
- Effect
- sensitive
- Status
- Reference
- Path
- 2.14
Purpose
What this entry explains
What it does
This reference explains Release Token Override for tabs, active targets, and claim state. 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 handle the sensitive path "Release Token Override" for tabs, active targets, and claim state.
- 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.
Release Token Override describes a gate for tabs, active targets, and claim state. 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 Release Token Override 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: claim.session_mismatch, releaseAuthorization. Safety axes: Browser state, Sensitive, 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 touches data, identity, or permissions in tabs, active targets, and claim state that may be used only with clear purpose.
The agent starts with nova.tab_new, reads the current response or reference, and only then chooses the concrete next tool.
Sensitive values stay in current scope; they are not guessed, logged, or copied into other contexts.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 |
|---|---|
claim.session_mismatch | Runtime or communication signal for agent-facing integrations. It is not a normal human UI control. |
releaseAuthorization | Response field named by the catalog source. Treat it as current evidence for the next decision. |
Safety
Boundary before execution
May touch sensitive data, permissions, credentials, identity, or external connection paths. Use only with explicit scope and visible user control.
Require explicit purpose and current context, avoid exposing secrets in prompts or logs, and stop when permission or identity state is unclear.
For humans, this entry marks the sensitive surface in tabs, active targets, and claim state and keeps permission, credential, or external-connection handling explicit.
High-Impact Review
Execution boundary and recheck hints
Review category: Vault/credentials
Credentials, tokens, and secrets may be used only for the named purpose and current target context.
False assumption: a stored value may be copied into prompts, logs, or third-party tool chains.
Purpose, target site, identity context, and approval must be reviewable by the user.
Do not guess, display, log, or forward secrets; use only protected fill or check paths with current scope.
Stop when identity, domain, approval, or expected input location is not unambiguously visible.
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.sensitive_data
Touches cookies, storage, clipboard, credentials, tokens, user content, identity, or private data.
Use only with bounded purpose and visible user control; do not guess, log, or forward sensitive values.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.