wp_plugin_deactivate · Wp Cli MCP: Risk & Policy

WHAT IT DOES

What wp_plugin_deactivate does on Wp Cli

AI agents use wp_plugin_deactivate to create or update resources in Wp Cli — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wp Cli environment.

WHY IT NEEDS A POLICY

Why wp_plugin_deactivate needs a policy

Deactivating a plugin modifies WordPress configuration state (active plugins list) but does not delete or destroy data/code. The action is reversible via reactivation, placing it in Write rather than Destructive. However, deactivating critical plugins could break site functionality, warranting medium severity.

From the tool's definition Tool name 'wp_plugin_deactivate' and description states it 'deactivate[s] an active WordPress plugin' - a modification operation. The description explicitly notes 'plugin files remain on disk and can be reactivated later', confirming the action is reversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wp_plugin_deactivate Rate-limited

wp_plugin_deactivate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_deactivate": {
      "limits": [
        {
          "counter": "wp_plugin_deactivate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_deactivate

What does the wp_plugin_deactivate tool do? +

Deactivate an active WordPress plugin without removing it. The plugin files remain on disk and can be reactivated later. It is categorised as a Write tool in the Wp Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wp_plugin_deactivate? +

Register the Wp Cli MCP server in PolicyLayer and add a rule for wp_plugin_deactivate: 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_deactivate? +

wp_plugin_deactivate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wp_plugin_deactivate? +

Yes. Add a rate_limit block to the wp_plugin_deactivate 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_deactivate completely? +

Set action: deny in the PolicyLayer policy for wp_plugin_deactivate. 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_deactivate? +

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