MCP Path

Transport Auth/Origin/Loopback

Transport Auth/Origin/Loopback is a public reference for connection setup, tool discovery, and transport readiness. 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: Basics & Session
Effect: changes state
Status: Reference
Path: 1.15

Purpose

What this entry explains

What it does

This reference explains Transport Auth/Origin/Loopback for connection setup, tool discovery, and transport readiness. 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 "Transport Auth/Origin/Loopback" for connection setup, tool discovery, and transport readiness.
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

Transport Auth/Origin/Loopback describes a gate for connection setup, tool discovery, and transport readiness. 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 Transport Auth/Origin/Loopback 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: 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 touches data, identity, or permissions in connection setup, tool discovery, and transport readiness that may be used only with clear purpose.

The agent starts with initialize, reads the current response or reference, and only then chooses the concrete next tool.

initialize nova.tools_bundle nova.app_info

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 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

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 connection setup, tool discovery, and transport readiness 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

Execution boundary

External targets, proxies, gateways, and transport paths may be used only with checked target, status, and approval.

Typical false assumption

False assumption: a reachable external tool is automatically part of the allowed Nova tool chain.

Visible user control

Target, transport status, import or connection approval, and expected data movement must be visible.

Agent rule

Do not silently add third-party tools; check current approval, target, and response status before use.

Abort or recheck

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