PAGUP Agent ControlWordPress access for AI assistants
Start free trial

Checklist Before Enabling an AI Assistant Inside a WordPress Plugin

Use this checklist before enabling an AI assistant inside a WordPress plugin. Activation is acceptable only when the product boundary, identity, credential lifecycle, allowed actions, forbidden actions, evidence owner and revocation path are all explicit.

Go or no-go criterion

Do not enable the assistant because the interface is present or because a connection test succeeds. The exit condition is a complete control record with no unknown owner, undocumented credential or untested refusal.

Before activation

  • Identify the host plugin, admin screen, installed version and official documentation for that version.
  • Separate the plugin’s assistant, any WAP Client integration, any MCP server and any remote backend.
  • Document the data sent, endpoint, consent step, retention statement and available actions. Mark absent evidence as unverified.
  • Assign a dedicated WordPress user; do not reuse a human administrator merely for convenience.
  • Name every credential by integration and purpose, and record who creates, rotates and revokes it.
  • Map each approved action to the required route, method, ability or tool and WordPress capability.
  • Define a forbidden action that must remain refused.
  • Assign the activation decision, evidence review and rollback to named owners.

Acceptance tests

  1. Confirm that the authenticated request resolves to the intended WordPress user.
  2. Execute one narrow approved read and retain a sanitized response.
  3. Attempt the predefined forbidden action and confirm that it is refused.
  4. Revoke the test credential and confirm that the same credential can no longer authenticate.
  5. Re-enable only with the final named credential and record its creation date and purpose.

Stop conditions

Stop if the integration cannot be tied to official versioned documentation, the credential owner is unknown, the required action needs broader access than approved, the refusal test succeeds unexpectedly, revocation recreates a credential without an understood trigger, or evidence would expose a secret or personal data.

Activation record

FieldRequired evidence
Product boundaryPlugin, WAP library, backend, connector and versions
IdentityDedicated WordPress username, role and relevant capabilities
ActionsApproved and forbidden route, method, ability or tool
CredentialLabel, owner, purpose, creation date and revocation trigger; never the secret
DecisionApprover, date, acceptance results and rollback owner

Sources and verification

This page was checked against the following primary sources. Last source review: .