Description
AI agents now run store work: support bots issue refunds, automations reprice products, MCP servers create coupons. Agentic Daisy AI Agent Firewall intercepts their writes, asks your rules, and holds the risky ones for a person. This add-on teaches it what those writes mean for a WooCommerce store.
Rules on what an action is worth
- “Refunds over $50 need my approval.”
- “Price cuts deeper than 20% need approval.”
- “Percent coupons over 30%, and coupons with no usage limit, need approval.”
- “No agent may create webhooks or change payment gateways.”
- “An agent may refund at most $300 a day” – a budget that catches a large refund split into small ones.
Amounts are computed from the store, never taken from what the agent claims, and an amount nobody can know is treated as large.
A refund guard that stops money before it moves
Every refund an agent makes – through the REST API, admin screens, an order set to “refunded”, or another plugin’s code – is decided before WooCommerce saves it and before the payment gateway is called. A held refund runs on approval exactly as it was requested, after checking that the order has not changed since.
Everything an agent can write
- WooCommerce’s REST API (v1 to v4), its admin API and its abilities, in any letter case, and batch requests item by item.
- Orders, products, coupons and their price and stock values, when an agent writes them through admin screens or another plugin rather than the REST API.
- WooCommerce REST API keys: bind a key to an agent, and its requests are that agent’s – on WooCommerce’s own MCP endpoint too.
- In-site MCP plugins: Cowboy MCP (1.7.4 up to 1.8), Royal MCP (1.5.10 up to 1.6) and AI Engine (3.8.6 up to 3.9). Their agents are identified, their store tools decided as store writes, and any other tool held for approval. Outside those versions the adapter stays off and says so.
Honest undo
Price changes, coupon changes, trashed items and store settings can be undone from the firewall’s ledger. Stock is adjusted by what the agent changed it by, so sales made since are kept. Gateway refunds, permanent deletes and emails to customers are marked irreversible before you approve them; order status changes are listed with the emails and stock moves they set off.
Works with your store
- HPOS (custom order tables) and posts storage alike.
- Cart and Checkout blocks.
- Multisite.
- Orders in another currency are measured at the order’s stored exchange rate (WooPayments multi-currency, or a filter for other plugins). An order with no stored rate is held for approval rather than measured.
It requires WooCommerce and Agentic Daisy AI Agent Firewall 2.1.0 or later. Everything here works with the free Agent Firewall.
Screenshots
FAQ
Who approves a held action?
Shop managers approve held product, order, coupon and note changes – never the one an agent is linked to. A refund the payment gateway would pay needs the “approve refunds” capability, which administrators have and you can grant to other roles. Settings, payment gateways, webhooks and API keys stay with administrators.
Does it change anything when a person makes a refund?
No. Only AI agents’ actions are decided. A person refunding an order in wp-admin is never held.
Which rules do I start with?
One click on Agent Firewall’s Policies screen applies a recommended set – refund threshold, daily refund budget, price change and coupon limits, denials for webhooks and payment gateways – as an ordinary Agent Firewall policy you can edit or delete. Before you apply it, it shows what the rules would have done to the last week of agent activity, and once your store has orders it suggests a refund threshold from your average order.
What about WooCommerce Subscriptions?
Subscriptions themselves are not decided yet. Refunds of renewal orders are: they are WooCommerce refunds like any other.
Which AI agents and MCP plugins are supported?
Agents on WooCommerce REST API keys (n8n, Zapier, WooCommerce’s Claude agent, community MCP servers), on application passwords (WordPress’s MCP adapter), and on Cowboy MCP, Royal MCP and AI Engine. A credential those plugins run as an administrator – every Cowboy MCP key, AI Engine’s static token – binds only to an agent an administrator confirms runs as one; it can never touch the firewall, its riskiest writes are held, and tools that run code or SQL or edit files should be switched off, since no firewall inside WordPress can stop them. The exposure scan flags MCP plugins it has no adapter for.
What is not covered?
An agent that writes the database directly, deletes or trashes products and orders without the REST API, or calls a payment gateway’s refund outside WooCommerce’s refund function. Agents normally work through the REST API, which is covered.
What happens to my data when I uninstall?
The “approve refunds” capability is removed from every role. The add-on’s settings – API key and MCP plugin bindings – stay, as Agent Firewall keeps its own data, unless you opted in:
wp option update adaf_delete_data_on_uninstall 1(Agent Firewall’s switch, which also removes its data when it is uninstalled) orwp option update adafwc_delete_data_on_uninstall 1(this add-on only). The Activity Ledger, approvals and policies belong to Agent Firewall.Does it send data anywhere?
No. It calls no external service, and it neither generates nor runs code.
What does it read?
Your store’s own orders, products, coupons and settings, to work out what an agent’s action is worth. To tell which agent is acting, it reads – never changes – the credentials that WooCommerce’s REST API keys and the supported MCP plugins (Cowboy MCP, Royal MCP, AI Engine) store, in their own options and tables. It stores no credential of its own: a binding names a key or an app by its id.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Agentic Daisy AI Agent Firewall for WooCommerce” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Agentic Daisy AI Agent Firewall for WooCommerce” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.0
- WooCommerce actions classified for the firewall: refunds, orders, products, coupons, customers, settings, gateways, webhooks and more, through the REST API (v1 to v4), the admin API and abilities; batch requests item by item.
- Facts for rules: refund amounts, order status changes, price changes, stock movements, coupon terms, in the store’s own currency.
- Refund guard: every agent refund decided before the payment gateway is called; held refunds run on approval as requested.
- Drift checks and undo for orders, products, coupons and store settings, on HPOS and posts storage.
- Store writes outside the REST API decided where WooCommerce saves them.
- WooCommerce REST API keys bound to agents, on WooCommerce’s MCP endpoint too.
- Agents on Cowboy MCP, Royal MCP and AI Engine identified; tools the firewall cannot read held for approval.
- Recommended store rules, applied with one click.
- Shop managers approve store holds; gateway refunds need the “approve refunds” capability.
- Approval card with the order, customer, gateway and a before/after comparison; agent activity on the order screen.