MCP Tool
nova.ui_set_native_dialog_file_name
For browser environment, window state, and isolated execution surfaces, an agent uses this public tool to handle the sensitive path "Native Dialog File set". It keeps purpose, scope, user control, and sensitive data handling explicit.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Window & UI Shell
- Effect
- sensitive
- Status
- Explained
- Path
- 24.7
Purpose
What this entry explains
What it does
nova.ui_set_native_dialog_file_name
An agent uses this tool to handle the sensitive path "Native Dialog File set". It belongs to browser environment, window state, and isolated execution surfaces; agents should combine it with current discovery, target awareness, and the visible result.
Use when
- Use this entry when an agent needs to handle the sensitive path "Native Dialog File set" for browser environment, window state, and isolated execution surfaces.
- 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 browser environment, window state, and isolated execution surfaces can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with nova.ui_get_state, 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
text
Text value for input or message. Use sensitive content only with a clear purpose.
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
May touch sensitive data, permissions, credentials, identity, or external connection paths. Use only with explicit scope and visible user control.
Require explicit purpose and current context, avoid exposing secrets in prompts or logs, and stop when permission or identity state is unclear.
For humans, this entry marks the sensitive surface in browser environment, window state, and isolated execution surfaces and keeps permission, credential, or external-connection handling explicit.
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.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
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.