This record as markdown: /tools/aapanel-mcp/plugin-uninstall.md
What plugin_uninstall does on Aapanel
AI agents call plugin_uninstall to permanently remove resources in Aapanel, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why plugin_uninstall is rated Critical
Uninstalling software is irreversible without a backup or reinstallation process. An AI agent calling this tool could disable critical services or remove security tools, causing operational damage. This is destructive rather than merely Execute because the action fundamentally removes system components.
From the tool's definition Tool name 'plugin_uninstall' and description 'Uninstall a software/plugin' indicate removal of installed software without reversibility. Uninstalling removes files and configurations that cannot be easily restored.
Attacks that exploit this kind of access
The rule that runs plugin_uninstall safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For plugin_uninstall, this is the rule to start with:
plugin_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 Aapanel, apply this rule, and every plugin_uninstall call is checked against it from then on.
Questions about plugin_uninstall
Uninstall a software/plugin. It is categorised as a Destructive tool in the Aapanel MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aapanel MCP server in PolicyLayer and add a rule for plugin_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 Aapanel. Nothing to install.
plugin_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 plugin_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 plugin_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.
plugin_uninstall is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
Across the catalogue