Responses & errors
Raqvio Agent Guardrails returns standard WordPress errors. Denial messages start with “Blocked by Raqvio Agent Guardrails: ” followed by the reason, because MCP clients only receive the message text.
| Code | HTTP | When | Example message |
|---|---|---|---|
raqvio_ag_blocked |
403 | The kill switch is on | Blocked by Raqvio Agent Guardrails: The Raqvio Agent Guardrails emergency kill switch is on: all AI agent actions are blocked. |
raqvio_ag_denied |
403 | Denied by a rule, the agent’s permission or default, the unknown-agent defaults, or a paused agent | Blocked by Raqvio Agent Guardrails: Agent permission for this ability: deny. |
raqvio_ag_approval_required |
202 | Pro: waiting for a human | This action needs human approval. It has been queued as approval_id 12; poll raqvio-ag/get-approval-status with that approval_id. |
raqvio_ag_engine_error |
503 | Raqvio Agent Guardrails itself failed while deciding a non-read call, so it blocked it for safety | Raqvio Agent Guardrails could not evaluate this request and blocked it for safety. |
For raqvio_ag_blocked and raqvio_ag_denied, the error data includes request_id (to find the call in the audit log) and rule_id when a rule decided. raqvio_ag_approval_required includes approval_id, poll_ability and rule_id.
Reasons you’ll see
Section titled “Reasons you’ll see”| Reason | Source |
|---|---|
| Agent permission for this ability: allow/deny. | The agent’s permission matrix |
| Agent default for unlisted abilities. | The agent’s “Abilities not listed in the matrix” setting |
| Default policy for write abilities. (read/financial/destructive) | Unknown-agent defaults, or an agent set to “Use risk defaults” |
| Matched policy rule “…”. | A Pro rule |
| This agent is paused. | Agent status |
| This action requires human approval, which is not available on this site. | “Require approval” without Pro |
| This action requires human approval, which could not be requested. | The approval request couldn’t be created |
| The WooCommerce API key this agent uses does not allow this operation, so it was not sent for approval. | Pro, WooCommerce MCP: the key’s read/write scope doesn’t cover the call |
| The Raqvio Agent Guardrails emergency kill switch is on: all AI agent actions are blocked. | Kill switch (raqvio_ag_blocked) |
Fail-safe behaviour
Section titled “Fail-safe behaviour”If Raqvio Agent Guardrails hits an internal error, read abilities are allowed (so a fault doesn’t take your store’s data offline) and everything else — write, financial, destructive — is blocked. Both are logged.
Other statuses in the audit log
Section titled “Other statuses in the audit log”If Raqvio Agent Guardrails allows a call but the ability’s own WordPress permission check refuses it — the agent’s user lacks the capability — the agent gets WordPress’s own error and the audit log records permission_denied.