execute_wp_cli · LocalWP MCP: Risk & Policy

WHAT IT DOES

What execute_wp_cli does on LocalWP MCP

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

This tool executes external commands (WP-CLI) whose effects are entirely dependent on the command arguments provided by the user. While not inherently destructive, WP-CLI commands can be destructive, financial, or have other significant side effects depending on what is executed.

From the tool's definition Tool name 'execute_wp_cli' and description 'Runs a WP-CLI command against the selected LocalWP site' indicate execution of arbitrary commands.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_wp_cli Rate-limited

execute_wp_cli 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": {
    "execute_wp_cli": {
      "limits": [
        {
          "counter": "execute_wp_cli_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 LocalWP MCP, so you can run agents against it safely.

FAQ

Questions about execute_wp_cli

What does the execute_wp_cli tool do? +

Runs a WP-CLI command against the selected LocalWP site using that site. It is categorised as a Execute tool in the LocalWP MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_wp_cli? +

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

What risk level is execute_wp_cli? +

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

Can I rate-limit execute_wp_cli? +

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

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

execute_wp_cli is provided by the LocalWP MCP server (kazimshah39/localwp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.