MCP Tool
nova.explore_surface
For risk-bounded actions with visible user control, an agent uses this public tool to carry out the bounded step "Close with health check". It separates target confirmation, intended state change, and verification after execution.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Surface Explorer (High Risk, Opt-in)
- Effect
- changes state
- Status
- Explained
- Path
- 28.4
Purpose
What this entry explains
What it does
nova.explore_surface
An agent uses this tool to carry out the bounded step "Close with health check". It belongs to risk-bounded actions with visible user control; 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 "Close with health check" for risk-bounded actions with visible user control.
- 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
An agent prepares a bounded run in risk-bounded actions with visible user control and must keep scope, progress, and stop condition visible.
The agent starts with nova.explore_surface, reads the current response or reference, and only then chooses the concrete next tool.
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
mode
Execution or read mode. Confirm it against current tool discovery before use.
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
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 risk-bounded actions with visible user control that may change, so the action can be reviewed before and after execution.
High-Impact Review
Execution boundary and recheck hints
Review category: Auto-apply/mutating flows
Mutating steps may run only with confirmed target, expected effect, user control, and result check.
False assumption: a guard or auto-apply signal replaces current target and result checks.
The user must be able to review action, target, approval, block signal, and visible result.
Execute only the intended step, then verify state and stop on warning, block, or target change.
Recheck if candidate budget, gate, visible state, or expected effect do not line up.
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.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.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.