Skip to content
WP Visibility

Review and control

Stop the Assistant Now

One button pauses every assistant tool call. Guard mode decides whether supported writes wait for you, the hourly write limit bounds how many get through, and revoking the password ends the connection.

Updated September 27, 2026

Docs

Click Pause all agent access in the Assistant connection section of the settings, or Pause agent on the Review queue status bar when Autopilot is on. From that moment every assistant tool call is refused, reads included, until you resume. The Abilities REST route answers with agent_paused; the plugin’s built-in MCP endpoint reports a permission error, ability_invalid_permissions. If you want the connection gone rather than paused, revoke the assistant’s Application Password as well.

The four controls

Pause. The kill switch. It stops ability execution for every connected client at once. Resume with Resume agent access in the same settings field, Resume agent on the status bar, or:

wp visibility agent resume

Pausing does not revoke anything. A connected administrator credential can reach the plugin’s separate resume route, so for an assistant you no longer trust, revoke its password too.

Guard mode. Guard mode needs the Autopilot module, which is off by default; while it is off there is no queue and assistant writes apply directly. In the Autopilot section, Assistant changes has two values. Hold for my review, the default, queues the supported write abilities as proposals: post SEO fields, bulk SEO updates, settings, creating and deleting redirects, llms.txt and the AI crawler policy. Apply immediately lets those same abilities write without the queue. Check which one is selected before you connect a client or start a batch.

The write limit. Assistant write limit (per hour) caps write ability requests per WordPress user and client label. The counter expires an hour after the last write request it allowed, rather than resetting on the hour. Requests over the limit are refused with rate_limited (HTTP 429 on the Abilities REST route) and the requested change is not made. Zero turns the limit off. It bounds request volume; it does not limit direct WordPress routes.

The approval ability. The ability that lets an assistant approve proposals ships disabled. Leave it that way unless you have a specific reason: an assistant that can approve its own proposals has no reviewer.

What pausing covers

The pause applies to the ability surface: everything an assistant reaches through the plugin’s MCP endpoint and the WordPress Abilities API. An Application Password lets a tool authenticate as its WordPress user (WordPress Advanced Administration Handbook, checked September 27, 2026), and pausing does not turn an administrator’s password into a restricted credential; core WordPress routes and the plugin’s own REST routes stay open to whatever that user may do. The user’s role is the outer boundary, and the pause is the inner one.

A sensible order when something goes wrong

  1. Pause. No ability call can run until you resume.
  2. Read the activity log to see what happened and when.
  3. Revert the applied proposals you do not want.
  4. Revoke the password if the client should not come back, then resume for the others.