Version 1.11.1 came out late on 8 November 2026 (GMT), and it is a safety and correctness release. Order creation joins the high-risk lock, the page-builder guard now covers ten builders, and bad input such as a broken URL is refused with a reason instead of being saved.
No tool was added, removed or renamed. The catalog is still 184 abilities, 90 in core and 94 from integrations.
Agent Abilities for MCP is a free WordPress plugin that lets Claude or ChatGPT work on your site as a WordPress user you pick, with this plugin’s own tools off until you turn them on. Updating needs no setup, but a few tools an agent could reach before are now held.
Takeaways:
- The high-risk lock now holds Create order, which makes ten native WooCommerce tools, and tools from other plugins: WooCommerce’s order status tool, its order update tool if your WooCommerce registers it, and six Secure Custom Fields tools for post types and taxonomies.
- Create order is out of the Shop manager access preset altogether. Post tools no longer reach a page, product, event, venue, organizer or listing while that type’s own tool is off.
- Writes to WPBakery, Bricks, Oxygen, Breakdance and Brizy pages are refused too, except an edit that only sets the excerpt.
- Invalid URLs, an event that ends before it starts and a sale price above the regular price are refused, and nothing is saved.
The high-risk lock holds more
The high-risk lock is a switch under Settings. Through this plugin’s own tools, WooCommerce tools that move money or grant authority stay unreachable until you unlock them, even if you have ticked them. High-risk lock and read-only mode, explained covers it in full.
Create order was not in the set until now. It joins refunds, order status and order updates, customer updates, payment gateways, coupons and tax rates, which makes ten native tools, up from nine. The explainer linked above was written when the set was nine.
The lock also reaches other plugins’ tools:
| Now held | What it is |
|---|---|
woocommerce/order-update-status, and woocommerce/orders-update where WooCommerce registers it |
WooCommerce’s own order status and order update tools, which change an order the way the locked native tools do. Current WooCommerce registers the second one only on its own MCP route, so it is held in advance. |
Six scf/ tools: create, update and import for post types and for taxonomies |
Secure Custom Fields tools that accept a callback name, which WordPress runs on that type’s edit screen |
While the lock is on, these rows show a lock and no switch on the Other plugins tab, and this plugin does not serve those tools. Your saved selections are not rewritten, so unlocking restores what you had.
Developers: the aafm_high_risk_abilities filter now accepts other plugins’ slugs. It can add to the locked set, never remove from it.
Post tools stop at a type’s own switch
Update post, Replace in post, Replace block and Update CPT item could change a page, product, event, venue, organizer or GeoDirectory listing even when the update tool built for that type was off. Now they reach one only while that type’s own update tool is on for the connection. Trash post is held the same way for pages, products and events, and Delete post for pages and products.
A read gap closes too. A role holding only read_private_posts no longer sees other people’s drafts, pending or scheduled posts through Get posts or Search content. Only users who may edit them see those.
Ten page builders are guarded
Since 1.7.4, an agent’s write to a page that a builder owns is refused with an error naming the builder, because the write could report success and change nothing. 1.11.1 adds WPBakery, Bricks, Oxygen, Breakdance and Brizy to Elementor, Divi, Beaver Builder, Avada and Visual Composer.
Since 1.12.0 (2026-11-15): Avada and WPBakery Page Builder pages now have their own editing tools, and Restore revision works on them; the other eight builders are still refused. The same release fixed Divi detection, which had looked for a meta key Divi never stores, so from 1.7.4 through 1.11.2 a write to a Divi page was not refused. See Page builders and the changelog.
There is one exception. Update post, Update page and Update CPT item accept an edit on a builder-owned post that sends only the id and the excerpt. The post’s stored content and title stay as they were. Any other field is refused, and so is every edit when the plugin cannot tell which builder owns the post.
If another plugin changes the stored content during the save, the plugin puts the post back and says nothing was changed. If it cannot confirm the restore, it returns an error telling you to check the post in the builder.
Bad input is refused, not saved
These now return an error and write nothing:
| Input | Where |
|---|---|
A javascript:, data: or junk URL |
SEO canonical and social image fields, menu item links, venue and organizer websites |
| An event end before its start | The Events Calendar create and update |
| A sale price above the regular price | WooCommerce products and variations |
| A refund of zero, a coupon with no code, an order for a customer id that is not a user | WooCommerce |
Smaller fixes
- In the plugin’s own testing on a demo site, ChatGPT kept showing its old tool list after a Refresh while the bridged WooCommerce product create and update tools advertised a schema that began with oneOf. Those two tools now advertise one merged schema, ChatGPT’s Refresh lists them, and WooCommerce still validates the real input.
- A refused post, term or user meta key now says why: not exposed, on the deny list, or protected. For the first, it names the setting that exposes the key. The new message never repeats the key or a value.
- With Force draft on, the setting that makes agent-created content save as a draft, a new product variation saves as disabled and a request to publish a disabled one keeps it disabled. A draft variation would disappear from WooCommerce’s editor.
- Rank Math’s Get head now includes the post’s custom SEO title, when the theme supports title tags, and its meta description.
- Each built-in write tool records the id or slug it changed in the Activity Log, and the site-wide replace records how many posts. Finding what an agent did walks through the log.
- Test connection sends your login cookies only to your own site’s address.
After you update
Nothing is required. If you use the affected tools, check the lock under Settings and the held rows on the Other plugins tab. If ChatGPT still shows an old tool list, open Settings, Integrations, Plugins, pick the app and choose Refresh.
The full history is on the changelog. The release before this one was 1.11.0.
What this does not cover
The excerpt exception pins the post’s content and title. It does not stop a builder’s own save hooks from running. We have not audited those hooks for Elementor, Beaver Builder, Divi, Avada or Visual Composer, and we make no claim about the other five.
This plugin does not filter what another plugin’s tool returns, and that plugin still decides whether a call is allowed. Tools a plugin publishes straight to the MCP Adapter’s default server sit outside this plugin’s read-only mode, allowlists, IP allowlist, rate limit and audit log, though Pause all access still applies. See Abilities from other plugins.