MCP Tool
nova.site_mcp_connect_request
For bounded website review runs and discoverable result data, an agent uses this public tool to carry out the bounded step "MCP Connect Request". It separates target confirmation, intended state change, and verification after execution.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Crawler & Site Discovery
- Effect
- changes state
- Status
- Explained
- Path
- 9.16
Purpose
What this entry explains
What it does
nova.site_mcp_connect_request
An agent uses this tool to carry out the bounded step "MCP Connect Request". It belongs to bounded website review runs and discoverable result data; agents should combine it with current discovery, target awareness, and the visible result.
Use when
- Use this entry when an agent needs to carry out the bounded step "MCP Connect Request" for bounded website review runs and discoverable result data.
- 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 in bounded website review runs and discoverable result data can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with nova.crawl_start, reads the current response or reference, and only then chooses the concrete next tool.
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
domain
Domain or scope value for site-specific queries.
| Response field | Explanation |
|---|---|
user_approved | Response field named by the catalog source. Treat it as current evidence for the next decision. |
Safety
Boundary before execution
Can change browser, page, or workflow state. The target and expected result must be clear before execution.
Confirm the current target first, perform only the intended bounded action, and verify the resulting page or workflow state afterwards.
For humans, this entry names the browser or workflow state in bounded website review runs and discoverable result data 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
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.
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_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.automation_run
Starts or monitors crawls, sequences, schedulers, tasks, batches, or longer runs.
Keep scope, budget, progress, stop condition, and terminal status visible before and during the run.high_impact_execution
Runs or prepares JavaScript, CDP, plugin code, auto-apply, or other powerful execution paths.
Explicitly confirm current tool discovery, target, scope, user control, and result check before execution.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.