This record as markdown: /tools/hostinger-mcp/wp-plugins-uninstall.md
What wp_plugins_uninstall does on Hostinger
AI agents call wp_plugins_uninstall to permanently remove resources in Hostinger, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why wp_plugins_uninstall is rated Critical
Uninstalling plugins removes files and configuration irreversibly. While not data deletion in the traditional sense, it destroys the installed state of plugins and cannot be undone without reinstalling. This meets the Destructive category criterion of actions that 'cannot be undone'.
From the tool's definition Tool name 'wp_plugins_uninstall' and description 'Uninstall WordPress plugins' indicate irreversible removal of plugin data and functionality.
Attacks that exploit this kind of access
The rule that runs wp_plugins_uninstall safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wp_plugins_uninstall, this is the rule to start with:
wp_plugins_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 Hostinger, apply this rule, and every wp_plugins_uninstall call is checked against it from then on.
Questions about wp_plugins_uninstall
Uninstall WordPress plugins. It is categorised as a Destructive tool in the Hostinger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hostinger MCP server in PolicyLayer and add a rule for wp_plugins_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 Hostinger. Nothing to install.
wp_plugins_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 wp_plugins_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 wp_plugins_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.
wp_plugins_uninstall is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
Across the catalogue