Critical Risk →

mcp_uninstall

Remove an MCP server

How to control mcp_uninstall ↓

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.

Critical Risk

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

Documented attack patterns abuse exactly the kind of access mcp_uninstall gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and 1MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mcp_uninstall:

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

mcp_uninstall disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register 1MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the mcp_uninstall tool do? +

Remove an MCP server. It is categorised as a Destructive tool in the 1MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on mcp_uninstall? +

Register the 1MCP Server MCP server in PolicyLayer and add a rule for mcp_uninstall: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches 1MCP Server. Nothing to install.

What risk level is mcp_uninstall? +

mcp_uninstall is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit mcp_uninstall? +

Yes. Add a rate_limit block to the mcp_uninstall rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block mcp_uninstall completely? +

Set action: deny in the PolicyLayer policy for mcp_uninstall. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides mcp_uninstall? +

mcp_uninstall is provided by the 1MCP Server MCP server (1mcp-app/agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every 1MCP Server tool call.

Deterministic rules across all 17 1MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

17 1MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.