MCP Tool
nova.network_read
For page perception, diagnostics, and verifiable read signals, an agent uses this public tool to check the state or evidence for "Network Read". It explains which current signal can be used as evidence and when a follow-up step needs a fresh target check.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Read & Inspect Pages
- Effect
- read-only
- Status
- Explained
- Path
- 4.18
Purpose
What this entry explains
What it does
nova.network_read
An agent uses this tool to check the state or evidence for "Network Read". It belongs to page perception, diagnostics, and verifiable read signals; agents should combine it with current discovery, target awareness, and the visible result.
Use when
- Use this entry when an agent needs to check the state or evidence for "Network Read" for page perception, diagnostics, and verifiable read signals.
- Use it to understand the public tool name, its expected boundary, and the response signals to check.
- 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.
Family example
A task touches data, identity, or permissions in page perception, diagnostics, and verifiable read signals that may be used only with clear purpose.
The agent starts with nova.perceive, 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
limit
Limit for lists or result sets. Keep it small when only orientation is needed.
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
Reads current state or evidence. It should not be treated as permission to act without a fresh next-step check.
Use the response as current evidence, then choose a more specific next tool only after target, scope, and freshness are clear.
For humans, this entry explains what an agent reads in page perception, diagnostics, and verifiable read signals and which current signal should be checked before trusting the result.
High-Impact Review
Execution boundary and recheck hints
Review category: Proxy/external connection
External targets, proxies, gateways, and transport paths may be used only with checked target, status, and approval.
False assumption: a reachable external tool is automatically part of the allowed Nova tool chain.
Target, transport status, import or connection approval, and expected data movement must be visible.
Do not silently add third-party tools; check current approval, target, and response status before use.
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.
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.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
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.