MCP Tool
nova.proxy_create
For sensitive browser, identity, or session data, an agent uses this public tool to handle the sensitive path "Proxy create". It keeps purpose, scope, user control, and sensitive data handling explicit.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Proxy Management
- Effect
- sensitive
- Status
- Explained
- Path
- 7.1
Purpose
What this entry explains
What it does
nova.proxy_create
An agent uses this tool to handle the sensitive path "Proxy create". It belongs to sensitive browser, identity, or session data; 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 "Proxy create" for sensitive browser, identity, or session 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 sensitive browser, identity, or session data can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with nova.proxy_create, 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
name
Name for the target object. Check uniqueness before creating or changing it.
protocol
Public input field from the catalog source. Confirm the exact schema through current MCP discovery before execution.
host
Public input field from the catalog source. Confirm the exact schema through current MCP discovery before execution.
port
Public input field from the catalog source. Confirm the exact schema through 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
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 sensitive browser, identity, or session data and keeps permission, credential, or external-connection handling explicit.
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.
persistent_change
Saves, deletes, remembers, schedules, or changes data that may outlive the immediate page state.
Execute only with clear scope and keep the saved, deleted, or scheduled effect reviewable.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.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.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.