wp_deactivate_plugin

Deactivate an installed plugin (via cvrt-mcp-endpoints)

SERVERWordpress SOURCE@cavort-it-systems/wordpress-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/wp-deactivate-plugin.md

WHAT IT DOES

What wp_deactivate_plugin does on Wordpress

AI agents invoke wp_deactivate_plugin to trigger actions in Wordpress. 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.

RISK

Why wp_deactivate_plugin is rated High

Deactivating a plugin alters site functionality and can break dependent features irreversibly.

From the tool's definition Deactivate an installed plugin

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wp_deactivate_plugin safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wp_deactivate_plugin, this is the rule to start with:

wp_deactivate_plugin Rate-limited

wp_deactivate_plugin 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_deactivate_plugin": {
      "limits": [
        {
          "counter": "wp_deactivate_plugin_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every wp_deactivate_plugin call is checked against it from then on.

FAQ

Questions about wp_deactivate_plugin

What does the wp_deactivate_plugin tool do? +

Deactivate an installed plugin (via cvrt-mcp-endpoints). It is categorised as a Execute tool in the Wordpress 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_deactivate_plugin? +

Register the Wordpress MCP server in PolicyLayer and add a rule for wp_deactivate_plugin: 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 Wordpress. Nothing to install.

What risk level is wp_deactivate_plugin? +

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

Can I rate-limit wp_deactivate_plugin? +

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

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

wp_deactivate_plugin is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →