Governed ability

Update post ACF fields

aafm/acf-update-post-fields Guarded write

Writes ACF field values on a post by field key, each value sanitized for its field type. Requires edit access to that post.

How it is governed

The same model as every ability in the plugin, stated for this one.

  • Off until you enable it

    Like every ability, Update post ACF fields ships switched off. You turn it on one at a time, and an update never widens access on its own.

  • Guarded write

    Writes stay conservative, and the plugin re-checks the capability before the call runs.

  • Capability gated

    A connection only sees Update post ACF fields if the user you connected can run it, and the plugin checks that capability again before it executes.

  • Every call audited

    The call is written to the log in your own database, denials included, with the argument keys but never the values.

See it in action

An illustrative run. Your real calls and data stay on your own site.

agent-abilities · audit Governed
You Update post ACF fields on this site.
Run Running aafm/acf-update-post-fields
Gate Allowed capability re-checked before running
Audit aafm/acf-update-post-fields · principal: editor · args: post_id, field_key
Result Applies the change, then writes the call to the audit log.

Try it with a prompt

Example requests you could paste to your agent.

  1. Set the subtitle ACF field on post 142 to "Built for busy teams".
  2. Update the event_date and location custom fields on this post.
  3. Write the new call to action text into the cta_label ACF field for post 512.

These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.

Frequently asked

Short answers for Update post ACF fields.

How are values written?

It writes ACF field values on a post by field key, and each value is sanitized for its field type before it is stored.

What stops it from editing any post?

It requires edit access to that specific post. It is a guarded write, off by default, and capability gated, and every write is captured in the audit log.

Does it work without ACF installed?

No. It exists only while Advanced Custom Fields is active. Deactivate ACF and the ability is no longer available.

Back to all abilities

Governed by default, from the first call.

Update post ACF fields is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.

Every ability off until you enable it, capability-gated on every call.