execute_wp_php_readonly · LocalWP MCP: Risk & Policy

WHAT IT DOES

What execute_wp_php_readonly does on LocalWP MCP

AI agents invoke execute_wp_php_readonly 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_readonly needs a policy

This tool executes PHP code within a WordPress environment. Although labeled 'read-only', PHP execution is inherently in the Execute category because: (1) it runs arbitrary code whose effects depend on the provided arguments, (2) PHP can have side effects beyond reads despite 'best-effort' restrictions (e.g., logging, caching, transient modifications), (3) the actual enforcement of read-only semantics is unclear…

From the tool's definition Tool description states 'Runs a best-effort read-only PHP snippet or PHP file inside the selected LocalWP site' - the verb 'Runs' indicates execution of arbitrary code within a site environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_wp_php_readonly Rate-limited

execute_wp_php_readonly 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_readonly": {
      "limits": [
        {
          "counter": "execute_wp_php_readonly_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_readonly

What does the execute_wp_php_readonly tool do? +

Runs a best-effort read-only 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_readonly? +

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

execute_wp_php_readonly 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_readonly? +

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

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

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