# mcp_uninstall

Remove an MCP server

Agent View of the PolicyLayer registry record for `mcp_uninstall`. HTML page: https://policylayer.com/tools/1mcp-app-agent/mcp-uninstall

## Facts

- Tool: `mcp_uninstall`
- Server: 1MCP Server (`1mcp-app/agent`) — https://policylayer.com/tools/1mcp-app-agent.md
- Homepage: https://github.com/1mcp-app/agent
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "mcp_uninstall",
    "arguments": {}
  }
}
```

## Why mcp_uninstall is rated Critical

Uninstalling an MCP server is a destructive operation that cannot be reversed without re-installing. While not as severe as deleting user data, removing infrastructure components that other tools depend on constitutes a destructive action with potential to disrupt service availability.

From the tool's own definition: "The tool 'mcp_uninstall' is explicitly described as 'Remove an MCP server', which irreversibly deletes or uninstalls a server instance. This action cannot be easily undone and results in the permanent removal of a server configuration."

## Use case

AI agents call mcp_uninstall to permanently remove resources in 1MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 1MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "mcp_uninstall"
  ]
}
```

## Other tools on 1MCP Server (16)

- `mcp_install` — Execute — https://policylayer.com/tools/1mcp-app-agent/mcp-install.md
- `mcp_reload` — Execute — https://policylayer.com/tools/1mcp-app-agent/mcp-reload.md
- `tool_invoke` — Execute — https://policylayer.com/tools/1mcp-app-agent/tool-invoke.md
- `mcp_info` — Read — https://policylayer.com/tools/1mcp-app-agent/mcp-info.md
- `mcp_list` — Read — https://policylayer.com/tools/1mcp-app-agent/mcp-list.md
- `mcp_registry_info` — Read — https://policylayer.com/tools/1mcp-app-agent/mcp-registry-info.md
- `mcp_registry_list` — Read — https://policylayer.com/tools/1mcp-app-agent/mcp-registry-list.md
- `mcp_registry_status` — Read — https://policylayer.com/tools/1mcp-app-agent/mcp-registry-status.md
- `mcp_search` — Read — https://policylayer.com/tools/1mcp-app-agent/mcp-search.md
- `mcp_status` — Read — https://policylayer.com/tools/1mcp-app-agent/mcp-status.md
- `tool_list` — Read — https://policylayer.com/tools/1mcp-app-agent/tool-list.md
- `tool_schema` — Read — https://policylayer.com/tools/1mcp-app-agent/tool-schema.md
- `mcp_disable` — Write — https://policylayer.com/tools/1mcp-app-agent/mcp-disable.md
- `mcp_edit` — Write — https://policylayer.com/tools/1mcp-app-agent/mcp-edit.md
- `mcp_enable` — Write — https://policylayer.com/tools/1mcp-app-agent/mcp-enable.md
- `mcp_update` — Write — https://policylayer.com/tools/1mcp-app-agent/mcp-update.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=1mcp-app-agent · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/1mcp-app-agent