Guard WooCommerce customer data from AI agents
Managing a store and editing a user are different powers. Here is why customer data belongs behind the capability that actually governs editing user accounts.
Read morePlain guides, governance notes, and honest use cases for running an AI agent against your own WordPress site.
Managing a store and editing a user are different powers. Here is why customer data belongs behind the capability that actually governs editing user accounts.
Read moreIn 1.6.2 we corrected a claim about the audit log. It keeps identifier-only values by design, never free-text content, and here is why that line matters.
Read moreVersion 1.6.2 corrects a claim about our own audit log, tightens who can edit customer data, and closes gaps in what the plugin records and sanitizes.
Read moreTwo controls decide what an AI agent is even offered on your WordPress site, before any per-call permission check runs: the high-risk lock and read-only mode.
Read moreA user-reported OAuth bug and six related fixes bring error responses, discovery, and tool status codes in line with what MCP and OAuth clients expect.
Read moreIn 1.4.3 an author-level user could read the entire WordPress media library, not just their own uploads. Here is the bug, the fix, and what else shipped.
Read moreIn 1.4.2 we fixed a bug where asking for a draft post published it live, two related permission gaps, and two WooCommerce order and product update bugs.
Read moreVersion 1.4.0 adds a one-screen Quick Connect wizard that gets an agent connected fast, without loosening the off by default governance underneath.
Read moreCopy-paste prompts for a freshly connected WordPress MCP server: safe reads, a careful draft write, and what a refusal looks like when an agent overreaches.
Read more