claudeus_wp_plugins__deactivate

Deactivate a plugin. Disable a currently active plugin without deleting it.

SERVERClaudeus WordPress MCP SOURCEdeus-h/claudeus-wp-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-plugins--deactivate.md

WHAT IT DOES

What claudeus_wp_plugins__deactivate does on Claudeus WordPress MCP

AI agents use claudeus_wp_plugins__deactivate to create or update resources in Claudeus WordPress MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claudeus WordPress MCP environment.

RISK

Why claudeus_wp_plugins__deactivate is rated Medium

Deactivating a plugin modifies the WordPress site's configuration by disabling active functionality, but does not delete the plugin. This is reversible (the plugin can be reactivated), placing it in Write rather than Destructive. However, severity is high because deactivating critical plugins (e.g., security, caching, authentication plugins) can break site functionality, expose vulnerabilities, or cause outages.

From the tool's definition Deactivate a plugin. Disable a currently active plugin without deleting it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs claudeus_wp_plugins__deactivate safely

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

claudeus_wp_plugins__deactivate Rate-limited

claudeus_wp_plugins__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": {
    "claudeus_wp_plugins__deactivate": {
      "limits": [
        {
          "counter": "claudeus_wp_plugins__deactivate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about claudeus_wp_plugins__deactivate

What does the claudeus_wp_plugins__deactivate tool do? +

Deactivate a plugin. Disable a currently active plugin without deleting it. It is categorised as a Write tool in the Claudeus WordPress MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on claudeus_wp_plugins__deactivate? +

Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_plugins__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 Claudeus WordPress MCP. Nothing to install.

What risk level is claudeus_wp_plugins__deactivate? +

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

Can I rate-limit claudeus_wp_plugins__deactivate? +

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

Set action: deny in the PolicyLayer policy for claudeus_wp_plugins__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 claudeus_wp_plugins__deactivate? +

claudeus_wp_plugins__deactivate is provided by the Claudeus WordPress MCP server (deus-h/claudeus-wp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claudeus WordPress, and thousands of servers like it.

This server

All 145 Claudeus WordPress tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →