acf_update_field_group
Update an existing ACF field group. Only the given group settings change. The endpoint re-imports the whole group through acf_import_field_group, which deletes stored fields whose key is not in the imported list, so pass the COMPLETE fields list (fields without a key get field_ + md5(group key + ...
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/acf-update-field-group.md
What acf_update_field_group does on Wordpress
AI agents use acf_update_field_group 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 acf_update_field_group is rated Medium
Modifies field group configuration and conditionally deletes fields not in import list.
From the tool's definition Update existing ACF field group; re-imports group, deletes stored fields
Attacks that exploit this kind of access
The rule that runs acf_update_field_group safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For acf_update_field_group, this is the rule to start with:
acf_update_field_group 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every acf_update_field_group call is checked against it from then on.
Questions about acf_update_field_group
Update an existing ACF field group. Only the given group settings change. The endpoint re-imports the whole group through acf_import_field_group, which deletes stored fields whose key is not in the imported list, so pass the COMPLETE fields list (fields without a key get field_ + md5(group key + name), matching ones made by acf_create_field_group). 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.
Register the Wordpress MCP server in PolicyLayer and add a rule for acf_update_field_group: 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.
acf_update_field_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the acf_update_field_group 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.
Set action: deny in the PolicyLayer policy for acf_update_field_group. 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.
acf_update_field_group is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wordpress, and thousands of servers like it.
This server
Across the catalogue