acf_update_fields · Wordpress MCP: Risk & Policy

WHAT IT DOES

What acf_update_fields does on Wordpress

AI agents use acf_update_fields to create or update resources in Wordpress — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wordpress environment.

WHY IT NEEDS A POLICY

Why acf_update_fields needs a policy

This tool creates or modifies ACF (Advanced Custom Fields) metadata on WordPress posts/pages. It is a Write operation because it reverses changes (fields can be updated again). Severity is medium because unintended field modifications could corrupt post metadata or trigger dependent business logic, but changes are reversible.

From the tool's definition Tool name 'acf_update_fields' and description explicitly states 'Use to update ACF custom fields' — a modification operation. Description confirms 'Write' categorization and notes it is 'blocked by WP_READ_ONLY', indicating it modifies data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

acf_update_fields Rate-limited

acf_update_fields 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": {
    "acf_update_fields": {
      "limits": [
        {
          "counter": "acf_update_fields_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 Wordpress, so you can run agents against it safely.

FAQ

Questions about acf_update_fields

What does the acf_update_fields tool do? +

Use to update ACF custom fields for a post or page. Write — blocked by WP_READ_ONLY. It is categorised as a Write tool in the Wordpress MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on acf_update_fields? +

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

What risk level is acf_update_fields? +

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

Can I rate-limit acf_update_fields? +

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

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

acf_update_fields is provided by the Wordpress MCP server (@adsim/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.