Abilities for agents

Raqvio Agent Guardrails registers three abilities in its raqvio-ag category (“Guardrail information for AI agents: permissions and approval status.”) plus a refund ability in WooCommerce’s category.

raqvio-ag/get-my-permissions

“Get my permissions”. Lets a well-behaved agent check what it may do before trying — fewer failed calls. Never blocked, never counted against rate limits, and it doesn’t reveal rule names.

Input: { "ability": "woocommerce/product-update" } (optional — omit for every ability)
Output:

{
  "governed": true,
  "agent": { "id": 3, "name": "Claude Desktop" },
  "kill_switch": false,
  "enforced": true,
  "abilities": [
    { "ability": "woocommerce/product-update", "decision": "allow", "reason": "Agent permission for this ability: allow.", "risk": "write" }
  ]
}

decision is allow, deny or require_approval. When a Pro rule decides, the reason is “A policy rule applies.” (rule names are never shown). Rules with conditions aren’t evaluated here; if one could apply, the entry lists the decisions such rules could make, e.g. "conditional": ["require_approval"], while decision shows what applies otherwise. enforced is false in audit-only mode.

Available over REST, the MCP Adapter, and WooCommerce’s MCP endpoint (raqvio-ag-get-my-permissions).

raqvio-ag/get-approval-status

“Get approval status”. Poll the result of a call that returned raqvio_ag_approval_required.

Input: { "approval_id": 1047 } (required)
Output (Pro): approval_id, status (pending, approved, executed, rejected, expired, failed), ability, expires_at, note, and — once executed or failed — result.
Only the identity that made the request can read it (same user, same agent, same application password); anyone else gets “Approval not found” (404).
In the free version there are no approvals, so it always answers raqvio_ag_approval_not_found.

Available over REST, the MCP Adapter, and WooCommerce’s MCP endpoint (raqvio-ag-get-approval-status).

raqvio-ag/order-create-refund

“Create order refund” — needs WooCommerce 10.9+. Registered the WooCommerce way, in the woocommerce category, and exposed to MCP through the MCP Adapter. It is governed (risk: financial, not reversible), so unknown agents are denied by default; pair it with the Pro template Approve refunds over X.

It requires the same permissions as WooCommerce’s REST refunds endpoint.

Input:

Field	Type	Notes
`id`	integer, required	Order ID
`amount`	decimal string	Refund amount, e.g. `"25.00"`. Omit to use the sum of the line items. For a full refund, pass the remaining refundable amount.
`reason`	string, ≤ 500 chars	Shown in the order notes
`line_items`	array, ≤ 100	`{ "id": order item ID (product, fee or shipping line), "quantity": for products, "refund_total": amount excluding tax }`
`refund_payment`	boolean, default `false`	Also return the money through the payment gateway — only if the gateway supports automatic refunds. By default the refund is only recorded in WooCommerce.
`restock_items`	boolean, default `false`	Put refunded quantities back in stock

Either amount or line_items is required. The amount must be positive and can’t exceed what is still refundable; line items must belong to the order.

Output: refund — id, order_id, amount, reason, refunded_payment, date_created_gmt, line_items — and order — id, status, currency, total, total_refunded, remaining_refund_amount.

Errors: raqvio_ag_order_not_found (404), raqvio_ag_refund_amount_required, raqvio_ag_refund_invalid_amount, raqvio_ag_refund_invalid_line_item, raqvio_ag_refund_gateway_unsupported (400), raqvio_ag_refund_failed.

Developers can turn it off with add_filter( 'raqvio_ag_register_refund_ability', '__return_false' );.

raqvio-ag/get-readiness-summary

“Get catalog readiness summary” — the store readiness score and top catalog issues: products, score, top_issues (id, label, count) and scan status. It requires the Raqvio Agent Guardrails manage capability, so it is meant for administrative tools rather than ordinary agents, and it is not exposed to MCP.