winget_uninstall
Uninstall a package by exact winget id (600s budget, tail of the output).
This record as markdown: /tools/mcp-hands/winget-uninstall.md
What winget_uninstall does on Mcp Hands
AI agents call winget_uninstall to permanently remove resources in Mcp Hands, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why winget_uninstall is rated Critical
An AI agent that decides to call winget_uninstall doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Hands is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs winget_uninstall safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Hands, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For winget_uninstall, this is the rule to start with:
winget_uninstall is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Hands, apply this rule, and every winget_uninstall call is checked against it from then on.
Questions about winget_uninstall
Uninstall a package by exact winget id (600s budget, tail of the output). It is categorised as a Destructive tool in the Mcp Hands MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Hands MCP server in PolicyLayer and add a rule for winget_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 Hands. Nothing to install.
winget_uninstall is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the winget_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.
Set action: deny in the PolicyLayer policy for winget_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.
winget_uninstall is provided by the Mcp Hands MCP server (huocai250/mcp-hands). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Hands, and thousands of servers like it.
Across the catalogue