wp_plugin_install · Wp Cli MCP: Risk & Policy

WHAT IT DOES

What wp_plugin_install does on Wp Cli

AI agents use wp_plugin_install 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_install needs a policy

Installing a plugin writes new code to the WordPress installation. If activated, it runs arbitrary PHP code on the server, which is effectively an Execute-level action. However, the installation itself is a Write operation (placing files). The 'activate immediately' option elevates severity significantly since it can execute arbitrary plugin code.

From the tool's definition Install a WordPress plugin from the official wordpress.org plugin directory. Optionally activate it immediately after installation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wp_plugin_install Rate-limited

wp_plugin_install 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_install": {
      "limits": [
        {
          "counter": "wp_plugin_install_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_install

What does the wp_plugin_install tool do? +

Install a WordPress plugin from the official wordpress.org plugin directory. Optionally activate it immediately after installation. 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_install? +

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

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

Can I rate-limit wp_plugin_install? +

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

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

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