cli_uninstall

Uninstall a CLI-Anything harness.

SERVERMcp Anything SOURCEZaymadkid/mcp-anything

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-anything/cli-uninstall.md

WHAT IT DOES

What cli_uninstall does on Mcp Anything

AI agents call cli_uninstall to permanently remove resources in Mcp Anything, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why cli_uninstall is rated Critical

Uninstalling a harness is a destructive operation that cannot be easily undone without reinstallation. While the blast radius is somewhat contained (affects only that specific CLI harness rather than the entire system), the irreversible nature and dependency implications justify the Destructive category and high severity.

From the tool's definition Tool name 'cli_uninstall' and description 'Uninstall a CLI-Anything harness' indicate removal of software/system components, which is irreversible.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cli_uninstall safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cli_uninstall, this is the rule to start with:

cli_uninstall Hidden

cli_uninstall is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cli_uninstall"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every cli_uninstall call is checked against it from then on.

FAQ

Questions about cli_uninstall

What does the cli_uninstall tool do? +

Uninstall a CLI-Anything harness. It is categorised as a Destructive tool in the Mcp Anything 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 cli_uninstall? +

Register the Mcp Anything MCP server in PolicyLayer and add a rule for cli_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 Mcp Anything. Nothing to install.

What risk level is cli_uninstall? +

cli_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 cli_uninstall? +

Yes. Add a rate_limit block to the cli_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 cli_uninstall completely? +

Set action: deny in the PolicyLayer policy for cli_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 cli_uninstall? +

cli_uninstall is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Anything, and thousands of servers like it.

This server

All 261 Mcp Anything tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →