Governed ability

Update term ACF fields

aafm/acf-update-term-fields Guarded write

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

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 term 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 term 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 term ACF fields on this site.
Run Running aafm/acf-update-term-fields
Gate Allowed capability re-checked before running
Audit aafm/acf-update-term-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 accent_color ACF field on category term 8 to #0066ff.
  2. Update the description_long custom field on this taxonomy term.
  3. Write a new icon value into the ACF fields for term 33.

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 term ACF fields.

How does the write behave?

It writes ACF field values on a term by field key, sanitizing each value for its field type before storing it.

What are the guardrails?

It requires edit access to that term, is a guarded write that is off by default, and is capability gated. Every write is logged.

Does it depend on ACF being active?

Yes. The ability is only registered while Advanced Custom Fields is active on the site.

Back to all abilities

Governed by default, from the first call.

Update term 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.