MCP Path

Fingerprint Validation & Policy

Fingerprint Validation & Policy is a public reference for browser identity, fingerprint surface, and profile impact. 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: Browser Identity (Persistent Identity Profiles)
Effect: sensitive
Status: Reference
Path: 45.15

Purpose

What this entry explains

What it does

This reference explains Fingerprint Validation & Policy for browser identity, fingerprint surface, and profile impact. 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 "Fingerprint Validation & Policy" for browser identity, fingerprint surface, and profile impact.
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

Fingerprint Validation & Policy describes a gate for browser identity, fingerprint surface, and profile impact. 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 Fingerprint Validation & Policy 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: level, set_global, set_sandbox, set_tab. Safety axes: 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 browser identity, fingerprint surface, and profile impact that may be used only with clear purpose.

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

nova.identity_get nova.identity_presets nova.identity_set

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

Safety

Boundary before execution

Effect

May touch sensitive data, permissions, credentials, identity, or external connection paths. Use only with explicit scope and visible user control.

Agent rule

Require explicit purpose and current context, avoid exposing secrets in prompts or logs, and stop when permission or identity state is unclear.

Human control

For humans, this entry marks the sensitive surface in browser identity, fingerprint surface, and profile impact and keeps permission, credential, or external-connection handling explicit.

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.

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