wp_plugin_activate · Wp Cli MCP: Risk & Policy

WHAT IT DOES

What wp_plugin_activate does on Wp Cli

AI agents invoke wp_plugin_activate to trigger actions in Wp Cli. 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 IT NEEDS A POLICY

Why wp_plugin_activate needs a policy

Activating a plugin executes its initialization code and hooks it into WordPress, which can trigger external operations, modify behavior, open attack surfaces, or run arbitrary PHP code. This is an operational state change that goes beyond a simple write and has potentially wide-ranging effects depending on the plugin being activated.

From the tool's definition Activate an installed but inactive WordPress plugin

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wp_plugin_activate Rate-limited

wp_plugin_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wp_plugin_activate": {
      "limits": [
        {
          "counter": "wp_plugin_activate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Wp Cli, so you can run agents against it safely.

FAQ

Questions about wp_plugin_activate

What does the wp_plugin_activate tool do? +

Activate an installed but inactive WordPress plugin. The plugin must already be installed. It is categorised as a Execute tool in the Wp Cli MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wp_plugin_activate? +

Register the Wp Cli MCP server in PolicyLayer and add a rule for wp_plugin_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 Wp Cli. Nothing to install.

What risk level is wp_plugin_activate? +

wp_plugin_activate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wp_plugin_activate? +

Yes. Add a rate_limit block to the wp_plugin_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.

How do I block wp_plugin_activate completely? +

Set action: deny in the PolicyLayer policy for wp_plugin_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.

What MCP server provides wp_plugin_activate? +

wp_plugin_activate is provided by the Wp Cli MCP server (mvtandas/wp-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.