What 1.11.0 adds: review the tools other plugins add

Version 1.11.0 came out on 6 November 2026, and it lets you review the tools other plugins add to your site before this plugin serves them to an AI agent. The Other plugins tab now says which plugin provides each group of tools, labels every tool Read, Write or Destructive, and lists tools that arrive with an update in a “New tools since your last review” card.

No tool was added, removed or renamed, so the catalog is still 184 abilities, 90 in core and 94 from integrations. This release is about the tools that other plugins register through the WordPress Abilities API. Abilities from other plugins calls that bridging, and the Bridge page lists which plugins have it.

Agent Abilities for MCP is a free WordPress plugin for owners who want Claude or ChatGPT to work on their site on terms they set. With 1.11.0, tools from other plugins arrive off, labelled and waiting for your review.

Takeaways:

  • Each group on the Other plugins tab names where its tools come from. Each tool is labelled Read, Write or Destructive, and a tool its plugin left unlabelled is treated as destructive and says so.
  • Tools that an update or a newly activated plugin adds wait in a “New tools since your last review” card. They were already off by default, and marking them reviewed does not switch them on.
  • Each plugin has an Allow only read tools button, the Activity Log can filter to one plugin, and an error from another plugin’s tool now names that plugin.
  • An upgraded site sees no card and no notification on day one. Everything already listed counts as reviewed.
  • This plugin does not filter what another plugin’s tool returns. The labels and marks are information for you, not a filter.

What the Other plugins tab shows now

Every group of tools from another plugin opens with a source line. It names the plugin when the plugin can be identified, and otherwise names the namespace, the text before the slash in a tool’s name.

You see What it tells you
“Provided by WooCommerce. Agent Abilities does not maintain these tools.” The plugin behind the group.
For a plugin it cannot identify, a line saying the tools come from a plugin that registers them under the namespace, for example writer The namespace, because naming a plugin would be a guess.
Read, Write or Destructive on each tool The label comes from the plugin’s own annotations.
“The plugin did not label this tool, so it is treated as destructive.” The plugin declared nothing about the tool.
“May return personal data.” A hint from the plugin and tool name.

The labels rest on annotations, hints a plugin attaches to its own tool. The Abilities API lets a plugin set readonly, destructive and idempotent, and the MCP Adapter turns them into MCP hints (MCP Adapter, creating abilities). The MCP specification says clients “MUST consider tool annotations to be untrusted unless they come from trusted servers” (Model Context Protocol, Tools).

That is why silence reads as destructive here. A label is only as good as the plugin author’s declaration, so a tool that declares nothing is not shown as safe.

The personal-data mark is a hint

The mark comes from the plugin and tool name. It is not detection and not a guarantee.

  • Whole namespaces: WPForms, Fluent Forms, Ninja Forms and SureForms.
  • An exact list of tools: WooCommerce orders, Stripe and PayPal payments, and Simple History.
  • Words in the tool name: learner, student, member, order, customer, user, contact, lead and similar. Built in, an LMS or membership tool is caught only by words like these, because we did not verify any LMS or membership namespace.

A tool with no mark can still return personal data. The notice on a marked group says as much: “treat any tool from another plugin as able to return personal data.”

New tools wait for your review

When a plugin update or a newly activated plugin adds tools, a card called “New tools since your last review” lists them, one block per plugin. Each tool shows its label, an “On” mark if you had already switched it on, and its personal-data notice.

Two buttons clear a block: Mark as reviewed for one plugin, and Mark all as reviewed. They record what you have seen and nothing more. Tools were already off until you switched them on, and the card’s own text says tools not marked On stay off, and that switching one on needs a Save.

Settings has a new notification trigger, “Another plugin adds new AI tools”. Notifications stay off until you choose how to be told, and the email alerts post covers the options.

If you choose the daily email, its count is a count of tools. It can read low when two plugins add tools within 15 minutes, because the second batch is throttled out of the email. The card still lists every tool, so treat the card as the full list.

Allow only read tools

Each active plugin’s group on the Other plugins tab now has an Allow only read tools button, and so does its block in the new-tools card. After a confirm, it sets that plugin’s enabled tools to exactly its read tools. Its other tools go off, and saved selections for its tools that are not on now are removed, so they do not come back later.

It applies as soon as you confirm, with no Save, and it touches no other plugin. A tool with no read-only label does not count as a read. If a plugin labels none of its tools read-only, the button turns all of them off, and the card says so.

OWASP lists the same idea under excessive agency: “Limit the extensions that LLM agents are allowed to call to only the minimum necessary.”

Find one plugin’s tools in the Activity Log

The Activity Log has a new Plugin filter. It lists this plugin’s core tools, each integration, an Other plugins (Bridge) bucket, and one entry for every plugin that is registered right now.

Core WordPress tools show as “WordPress”. Rows from a plugin you have since removed show under the existing Other plugins (Bridge) bucket, because the filter only covers plugins registered now. How to find what an AI agent did on your WordPress site walks through the rest of the log.

Errors name the plugin

A bridged tool’s error now says which plugin returned it, using the plugin’s name when it can be identified. For example, “WPForms Lite” replaces “wpforms”. When no plugin can be identified, the error names the namespace and says it is a namespace.

The QA Bridge Shop plugin returned an error: Test failure from the item store

That line came from a throwaway test plugin we wrote for the release test, not from a real plugin. An error that already names the plugin, errors from WordPress core’s own tools and core’s own validation errors are left as they were. Tool names, descriptions and schemas that clients see are unchanged.

Smaller fixes

  • The Quick Connect write note no longer promises that deletes go to Trash. It now reads “Turning this on adds no delete tools.”
  • The Upload media and Upload media from URL descriptions now say they require the upload-files capability.
  • The Content editor and Shop manager preset summaries now say playbooks. Reach did not change in this release, since 1.10.2 already added the two playbook tools to both presets.
  • The Get events description for The Events Calendar says drafts, pending and future events are limited to the caller’s own unless they can edit other people’s events, and two Avada descriptions lost a dash.

What we tested, and what we did not see

On 6 November 2026 we ran the release build on our demo site, demo.agentabilitieswp.com, from claude.ai and from ChatGPT, with the same result on both. The test used a throwaway plugin called QA Bridge Shop (5 tools) and WooCommerce 11.2.2 (7 tools).

  • The first admin load recorded the three WordPress core tools as reviewed and announced nothing.
  • QA Bridge Shop and WooCommerce each appeared in the new-tools card with Read, Write and Destructive labels, the “treated as destructive” note and personal-data notices.
  • The Allow only read tools confirm read “This turns on 3 read tools from QA Bridge Shop.” and “This turns on 2 read tools from WooCommerce.”
  • Both clients listed only the tools we had switched on. The list-items and products-query tools succeeded, the always-failing tool returned the error above, and a delete tool we left off was unavailable.
  • Filtering the Activity Log to QA Bridge Shop returned 4 entries, all from that plugin.

We did not see three things live. Email delivery of the new notification went untested. Narrow widths were not checked on the demo, though an earlier pass checked 390 and 360 pixels on a test site. And the consent screen’s wording for permanent deletes was not seen, because the demo has no permanent-delete tool switched on.

What this does not cover

This plugin does not filter what another plugin’s tool returns. A Read label says the plugin declared the tool read-only, and a personal-data mark is a hint, so neither limits what comes back.

Tools that a plugin publishes straight to the MCP Adapter’s default server are outside these controls as well. Read-only mode, allowlists, the IP allowlist, the rate limit and the audit log do not apply to them, though Pause all access does.

Updating

Update from the Plugins screen as usual. The first time an administrator opens wp-admin afterwards, the plugin records every tool already listed as reviewed, along with every saved selection, even one whose plugin is inactive. So you will see no card and no notification on day one, and nothing you switched on changes.

After that, detection runs when an administrator loads wp-admin, not on a schedule. If a WP-CLI command or an automatic update adds tools, the card and the notification wait for the next admin visit.

The full history is on the changelog. The release before this one was 1.10.2, and Abilities from other plugins covers the Other plugins tab itself.