WP-CLI
All commands live under wp ability-gate. Approving, rejecting and rolling back are recorded against a user, so pass --user=<admin>.
Requests#
wp ability-gate requests list --status=pending
wp ability-gate requests list --format=json
wp ability-gate requests approve <uuid> --user=admin
wp ability-gate requests reject <uuid> --reason="Not now" --user=admin
wp ability-gate requests rollback <uuid> --user=admin
wp ability-gate requests rollback <uuid> --force --ack-external --user=admin
--force rolls back even if rows changed since; --ack-external accepts that external effects are not undone. list takes --format=table|json|csv.
Audit trail#
wp ability-gate audit verify
wp ability-gate audit export --format=csv
wp ability-gate audit export --format=ndjson --since=2026-01-01 --file=audit.ndjson
--file writes to a file instead of the terminal; add --force to overwrite an existing file.
Agents#
wp ability-gate agents list
wp ability-gate agents set-mode app_password:<uuid> paused
Modes are paused, restricted and trusted.
Plain WP-CLI commands are not gated: they are run by someone with shell access. The exception is the MCP Adapter’s STDIO server, which is treated as an agent.
Was this article helpful?
Tell us what was missing
