WooCommerce stores just quietly became something AI agents can operate directly, and that puts hosting providers in an uncomfortable spot whether they asked for it or not.
The platform’s 10.9 release went stable on June 23, and buried in the changelog are seven new “abilities,” officially defined operations that let an agent, script, or automation tool query and modify products and orders through a standard interface. Five of those seven can write changes, meaning an agent with the right permissions can create products, delete them, update order status, or add notes, not just look things up. Because this ships by default through the normal upgrade cycle, every host running WooCommerce will have this surface live on customer stores whether the merchant ever thought about it or not.
That distinction matters more than it sounds. Before this update, developers building AI integrations had to work through the regular REST API, and every integration interpreted “create a product” or “update an order” slightly differently. Now there’s one official definition baked into the platform itself, the same one whether a human clicks through the admin panel or an AI agent connects through the Model Context Protocol.
The timing lines up with a broader concern security researchers raised earlier this month at Infosecurity Europe: prompt injection, where an agent gets manipulated by something it reads, isn’t really a bug anymore. It’s closer to a structural feature of how these systems work. So while WooCommerce built a cleaner, more governed way for agents to interact with stores, it also widened the door those agents walk through, and the security of that door now depends entirely on how carefully a hosting provider configures permissions on the MCP endpoint.
There’s good news for hosts buried in the release too. WooCommerce stopped creating throwaway draft orders during routine browsing sessions, a fix that should meaningfully cut database load on busy storefronts hosts pay to keep running. Email logging also moved into core, quietly reducing one of the most common support tickets hosts deal with.
For hosting providers, the real homework isn’t the feature list. It’s confirming who, or what, currently has permission to act on a merchant’s behalf.
