wordpress_activate_plugin · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_activate_plugin does on WordPress MCP Server

AI agents invoke wordpress_activate_plugin to trigger actions in WordPress MCP Server. 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 wordpress_activate_plugin needs a policy

Activating a plugin runs its activation hooks and code on the server, which is an Execute-class action. It can have wide-ranging side effects depending on what the plugin does (e.g., modifying the database, registering services). The description is empty, so confidence is slightly reduced, but the name strongly implies execution of plugin code.

From the tool's definition Tool name: 'wordpress_activate_plugin' — 'activate' implies triggering a state change on a plugin, which executes initialization code on the WordPress site.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_activate_plugin Rate-limited

wordpress_activate_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": {
    "wordpress_activate_plugin": {
      "limits": [
        {
          "counter": "wordpress_activate_plugin_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 WordPress MCP Server, so you can run agents against it safely.

FAQ

Questions about wordpress_activate_plugin

What does the wordpress_activate_plugin tool do? +

wordpress_activate_plugin. It is categorised as a Execute tool in the WordPress MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wordpress_activate_plugin? +

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

What risk level is wordpress_activate_plugin? +

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

Can I rate-limit wordpress_activate_plugin? +

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

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

wordpress_activate_plugin is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.