By Greg Nowak. Updated 2 November 2026.
An AI assistant that prepares a campaign page could save your team useful time. But preparing a draft, publishing it and exporting customer data are three very different responsibilities. Before connecting an agent to WordPress, decide exactly where its responsibility ends.
WordPress 7.1 improves how external tools discover registered actions through the Abilities API. For business owners and agency teams, the practical job is to agree which actions an integration needs, enforce those limits and give someone ownership of the workflow.
What WordPress 7.1 actually exposes
An ability is a registered operation with a description, inputs and an execution callback. WordPress 7.1 adds meta.public to indicate that an ability is intended for external clients. Setting it to true makes REST exposure default to true, while an explicit show_in_rest value takes precedence. Abilities with neither setting remain unavailable through REST. See the official exposure guidance.
The word “public” can mislead here. It describes client exposure, not anonymous permission to execute. All Abilities REST endpoints require authentication, and execution depends on the ability’s permission_callback. Discovering an action does not grant permission to run it.
Start with one workflow and an honest inventory
Write down a small, useful outcome: “Read approved product information and create a draft landing page.” Identify the content it can use, where the draft belongs and who reviews it. This gives your developer a concrete boundary to implement.
Then inventory the abilities registered by WordPress and active plugins. Record each ability’s owner, inputs, returned data, exposure settings, permission check and actual effect. A name such as “sync content” tells you little about whether it publishes or deletes anything.
Developers can use wp_get_abilities() with namespace, category or metadata filters. However, global filters can alter even an unfiltered call. For a complete registry inspection, after abilities have registered, use:
$registry = WP_Abilities_Registry::get_instance();
$abilities = $registry->get_all_registered();That distinction is documented in the 7.1 discovery changes. Compare the registry with the integration’s exposed view:
GET /wp-json/wp-abilities/v1/abilities?namespace=my-pluginUse an authenticated request and check every results page. A REST listing only shows exposed abilities; it is not the complete inventory.
Agree the boundary by business consequence
| Action | Example | Recommended starting boundary |
|---|---|---|
| Read approved information | Retrieve product facts | Allow within an agreed content scope |
| Create a recoverable draft | Prepare a landing page | Allow; return the draft link and log the outcome |
| Change public content | Publish a page or change pricing | Require approval of the exact proposed change |
| Handle sensitive data or deletion | Export users or delete records | Keep unavailable unless specifically required and reviewed |
Give the integration its own WordPress identity
For external access, use an application password over HTTPS, attached to a dedicated WordPress user with capabilities appropriate to the task. Avoid borrowing someone’s administrator account. Application passwords are individually revocable credentials tied to a user; creating one does not itself establish your workflow’s permission boundaries. The WordPress administration guide explains creation and revocation.
Enforce resource access inside each ability. For an operation on a particular post, a check such as current_user_can( 'edit_post', $post_id ) helps assess permission for that object. Validate inputs and enforce any additional restrictions on post types, statuses or permitted content.
Also review what else that identity can access through WordPress and plugins. Limiting the tools displayed to an agent does not constrain other routes available to its credentials.
Make approval enforceable
For publication, show the reviewer the target site, page and proposed content. Bind approval to that specific change; editing the proposal should require fresh approval. Recheck authorization when execution happens.
A prompt saying “ask before publishing” expresses intent. The server or integration must enforce the decision. For an initial rollout, letting the assistant create drafts while a person publishes through WordPress is often a manageable arrangement.
Use execution hooks without weakening permissions
WordPress 7.1 adds useful policy hooks. wp_pre_execute_ability can stop execution before validation and permission checks, making it suitable for a narrowly implemented integration shutdown. wp_ability_permission_result runs after the permission callback: preserve existing denials, because returning true can override them.
Input and result filters run before their respective schema validations. Follow the documented execution order when implementing these controls.
Test failures and retries before launch
In staging, use the integration’s actual identity. Confirm that the intended draft workflow succeeds, while publication, unrelated content changes and sensitive exports are denied. Try malformed input, revoked credentials and permissions changed between preparation and execution. Check the HTTP methods required by the Abilities REST endpoints, and compare annotations such as readonly and destructive with actual behavior.
Test a timeout followed by a retry. Could it create duplicate drafts or repeat a consequential action? Because output validation follows the callback, an output error may occur after a change has happened. Check the resulting state before retrying.
Record the caller, ability, target, approval reference and outcome without copying sensitive payloads into logs. Assign someone to review changes after plugin updates and revoke access when the integration is retired.
If your team is planning a WordPress AI workflow, Greg can help turn the proposal into an ability inventory, permission plan and staging acceptance checks. Get in touch with Greg to discuss a focused review.
Related on GrN.dk
- A Voice Agent Is Only Ready When the Human Handoff Works
- Before an AI Assistant Issues a Refund, Put Approval in Its Path
- Prompt Cache Write Costs: Check What Your Workflow Actually Reuses
Need help with this kind of work?
Discuss your WordPress AI workflow with Greg Get in touch with Greg.