Governed ability

Update content item

aafm/update-cpt-item Guarded write

Update an item of an allowlisted custom content type by ID (publishing requires that type's publish capability).

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 content item 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 content item 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 content item on this site.
Run Running aafm/update-cpt-item
Gate Allowed capability re-checked before running
Audit aafm/update-cpt-item · principal: editor · args: post_id
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. Update portfolio item 220 with this new description.
  2. Change the summary on event item 55.
  3. Edit testimonial 12 to fix the author name.

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 content item.

Can it publish the item?

Publishing requires that type's publish capability, otherwise it edits the item without taking it live.

How is access limited?

Only allowlisted types, only items the agent can edit, off by default, and every change is logged.

Back to all abilities

Governed by default, from the first call.

Update content item 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.