wp_call_function · LocalWP MCP: Risk & Policy

WHAT IT DOES

What wp_call_function does on LocalWP MCP

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

Despite being described as 'read-oriented', this tool executes arbitrary PHP/WordPress function calls inside a live site. The actual execution of code in a running WordPress environment can have side effects depending on the function called. 'Read-oriented' is a stated intent, not a technical constraint, so the true category is Execute.

From the tool's definition 'Runs a read-oriented function call inside the selected LocalWP site' — executes code within the WordPress environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wp_call_function Rate-limited

wp_call_function 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": {
    "wp_call_function": {
      "limits": [
        {
          "counter": "wp_call_function_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 wp_call_function

What does the wp_call_function tool do? +

Runs a read-oriented function call 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 wp_call_function? +

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

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

Can I rate-limit wp_call_function? +

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

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

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