MCP Tool

`nova.plugin_uninstall`

For extensions, external MCP sources, and bounded tool execution, an agent uses this public tool to handle the sensitive path "Plugin deinstallieren". It keeps purpose, scope, user control, and sensitive data handling explicit.

Agent tool

Canonical reference for a public MCP tool name.

Type: MCP tool
Family: Plugins (AAP)
Effect: sensitive
Status: Explained
Path: 15.10

Purpose

What this entry explains

What it does

nova.plugin_uninstall An agent uses this tool to handle the sensitive path "Plugin deinstallieren". It belongs to extensions, external MCP sources, and bounded tool execution; 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 "Plugin deinstallieren" for extensions, external MCP sources, and bounded tool execution.
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 extensions, external MCP sources, and bounded tool execution can trigger powerful execution and therefore needs target, approval, and result check before the step.

The agent starts with nova.plugin_create, reads the current response or reference, and only then chooses the concrete next tool.

nova.plugin_create nova.plugin_inspect nova.plugin_test

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

pluginId

Reference key for the current target, object, or session. Read it from the current response instead of guessing.

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

Effect

May touch sensitive data, permissions, credentials, identity, or external connection paths. Use only with explicit scope and visible user control.

Agent rule

Require explicit purpose and current context, avoid exposing secrets in prompts or logs, and stop when permission or identity state is unclear.

Human control

For humans, this entry marks the sensitive surface in extensions, external MCP sources, and bounded tool execution and keeps permission, credential, or external-connection handling explicit.

High-Impact Review

Execution boundary and recheck hints

Review category: Plugin runtime

Execution boundary

Plugin code and runtime calls stay limited to explicitly approved tools, permissions, and target contexts.

Typical false assumption

False assumption: an installed or loaded plugin may use all available browser data.

Visible user control

Approval, active tab, permission, and test result must remain visible user controls.

Agent rule

Execute plugin capabilities only after current tool discovery and permission checks; do not blindly chain external runtime output.

Abort or recheck

Recheck when permissions are missing, a plugin is unknown, or runtime status diverges from expected scope.

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 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 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.

High-impact execution 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 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.

nova.plugin_uninstall