execute_wp_php · LocalWP MCP: Risk & Policy

WHAT IT DOES

What execute_wp_php does on LocalWP MCP

AI agents invoke execute_wp_php 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_php needs a policy

PHP execution is a classic Execute category tool: it runs code whose effects are entirely argument-dependent. Unlike the read-only variant (execute_wp_php_readonly) also on this server, this tool lacks safety constraints and can invoke file operations, database modifications, plugin/theme changes, HTTP requests, and other side effects.

From the tool's definition Runs a high-trust PHP snippet or PHP file inside the selected LocalWP site — this permits arbitrary PHP code execution within a WordPress environment, which can trigger external operations, modify state, and access sensitive data depending on the code…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_wp_php Rate-limited

execute_wp_php 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_php": {
      "limits": [
        {
          "counter": "execute_wp_php_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_php

What does the execute_wp_php tool do? +

Runs a high-trust PHP snippet or PHP file inside the selected LocalWP 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_php? +

Register the LocalWP MCP server in PolicyLayer and add a rule for execute_wp_php: 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_php? +

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

Can I rate-limit execute_wp_php? +

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

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

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