This record as markdown: /tools/hostinger-mcp/wp-plugins-activate.md
What wp_plugins_activate does on Hostinger
AI agents invoke wp_plugins_activate to trigger actions in Hostinger. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why wp_plugins_activate is rated High
Activating a plugin triggers the plugin's activation hook and starts executing its code within WordPress. This is not a simple data write—it causes external operations and code execution on the server. It is reversible (plugins can be deactivated), so it doesn't qualify as Destructive, but it does execute plugin code and can have significant side effects depending on the plugin.
From the tool's definition Activate a WordPress plugin
Attacks that exploit this kind of access
The rule that runs wp_plugins_activate 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_activate, this is the rule to start with:
wp_plugins_activate stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every wp_plugins_activate call is checked against it from then on.
Questions about wp_plugins_activate
Activate a WordPress plugin. It is categorised as a Execute tool in the Hostinger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hostinger MCP server in PolicyLayer and add a rule for wp_plugins_activate: 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_activate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wp_plugins_activate 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_activate. 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_activate 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