Governed ability
Create WooCommerce order refund
aafm/wc-create-order-refund Guarded write
Creates a refund on a WooCommerce order by order id. Accepts an amount, optional reason, and optional line-item breakdown. Reason text is returned verbatim under the Integrations security disclaimer. Requires the manage-WooCommerce capability.
How it is governed
The same model as every ability in the plugin, stated for this one.
- Off until you enable it
Like every ability, Create WooCommerce order refund ships switched off. You turn it on one at a time, and an update never widens access on its own.
- Guarded write
Writes stay conservative, and the plugin re-checks the capability before the call runs.
- Capability gated
A connection only sees Create WooCommerce order refund if the user you connected can run it, and the plugin checks that capability again before it executes.
- Every call audited
The call is written to the log in your own database, denials included, with the argument keys but never the values.
See it in action
An illustrative run. Your real calls and data stay on your own site.
Try it with a prompt
Example requests you could paste to your agent.
Refund 25 on order 1088 for a returned item.
Issue a full refund on order 1088 with the reason customer changed their mind.
Create a partial refund on order 1088 for a single line item.
These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.
Frequently asked
Short answers for Create WooCommerce order refund.
Does this reach sensitive data?
It records a refund against an order, and the reason text is returned verbatim under the Integrations security disclaimer, so it is gated behind an admin notice.
Is refunding on by default?
No. It stays off until an administrator enables it, requires the manage-WooCommerce capability, and is bounded by the connected user's permissions.
Governed by default, from the first call.
Create WooCommerce order refund is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.
Every ability off until you enable it, capability-gated on every call.