MCP Path

Clipboard Global Provenance

Clipboard Global Provenance is a public reference for user artifacts, notices, and small work handoffs. 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: Favorites & Clipboard
Effect: read-only
Status: Reference
Path: 20.7

Purpose

What this entry explains

What it does

This reference explains Clipboard Global Provenance for user artifacts, notices, and small work handoffs. 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 check the state or evidence for "Clipboard Global Provenance" for user artifacts, notices, and small work handoffs.
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

Clipboard Global Provenance describes a gate for user artifacts, notices, and small work handoffs. 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 Clipboard Global Provenance 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: Read current 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 in user artifacts, notices, and small work handoffs can trigger powerful execution and therefore needs target, approval, and result check before the step.

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

nova.favorites_add nova.favorites_list nova.favorites_open

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

Effect

Reads current state or evidence. It should not be treated as permission to act without a fresh next-step check.

Agent rule

Use the response as current evidence, then choose a more specific next tool only after target, scope, and freshness are clear.

Human control

For humans, this entry explains what an agent reads in user artifacts, notices, and small work handoffs and which current signal should be checked before trusting the result.

High-Impact Review

Execution boundary and recheck hints

Review category: Clipboard/site data/cookies/storage

Execution boundary

Cookies, storage, cache, and clipboard stay limited to origin, purpose, and current user control.

Typical false assumption

False assumption: site data is only technical configuration and not user-related.

Visible user control

Origin, data kind, planned change, and expected effect must remain visible.

Agent rule

Do not guess, log, or reuse cookies, storage values, or clipboard contents across domains.

Abort or recheck

Stop if origin, value, delete effect, or target page does not clearly match the current task.

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.

Read current state read_current_state

Reads current state, response signals, or evidence without treating that alone as permission for a follow-up action.

Use the signal as current evidence and re-check target, scope, and visible state before any follow-up action.

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.