MCP Path

Reflection Gate

Reflection Gate is a public reference for agent warnings, blocks, and current approval signals. 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: AAG (Agent Awareness Gates)
Effect: read-only
Status: Reference
Path: 14.4

Purpose

What this entry explains

What it does

This reference explains Reflection Gate for agent warnings, blocks, and current approval signals. 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 "Reflection Gate" for agent warnings, blocks, and current approval signals.
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

Reflection Gate describes a signal for agent warnings, blocks, and current approval signals. 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 Reflection Gate 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. The reference path alone is not permission to execute. Before acting, check current MCP discovery, visible target, scope, and the actual response.

Family example

An agent prepares a bounded run in agent warnings, blocks, and current approval signals and must keep scope, progress, and stop condition visible.

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

nova.learn_resolve_opportunity nova.tabs Bootstrap-Warning

Scope, budget, progress, stop condition, and terminal status remain part of the run.

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 agent warnings, blocks, and current approval signals and which current signal should be checked before trusting the result.

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.