Report a checkout URL that you could not complete. Call this when you failed to finish a purchase — for any reason (field not found, bot blocked, timeout, unknown form). The URL will be logged for admin review to improve future checkout success rates. This is part of Z-ZERO's self-healing loop.
AI agents use report_checkout_fail to create or update resources in Z Zero — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Z Zero environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | The checkout/payment page URL where the purchase failed. |
error_type | string | Yes | Short error category: 'field_not_found', 'timeout', 'bot_blocked', 'unknown_form', 'price_mismatch', or 'other'. |
error_message | string | — | Brief description of what went wrong, e.g. 'Could not find card number field' or 'Page redirected to CAPTCHA'. |
Parameters from the server's own tool schema.
This tool writes data (logs a failed checkout URL and associated metadata) to a backend system for administrative review. It does not delete, move money, execute arbitrary code, or modify existing data; it only appends a diagnostic log entry. The blast radius is minimal—misuse would create spurious log entries but cause no financial, security, or operational harm.
From the tool's definition Tool description states: 'Report a checkout URL that you could not complete' and 'The URL will be logged for admin review' — this creates a log entry/record in the system.
Risk signalsAccepts URL/endpoint input (url) · Admin/system-level operation
Attacks that exploit this kind of access
Report a checkout URL that you could not complete. Call this when you failed to finish a purchase — for any reason (field not found, bot blocked, timeout, unknown form). The URL will be logged for admin review to improve future checkout success rates. This is part of Z-ZERO's self-healing loop. It is categorised as a Write tool in the Z Zero MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
report_checkout_fail accepts 3 parameters: url, error_type, error_message. Required: url, error_type. The full parameter table on this page comes from the server's own tool schema.
Register the Z Zero MCP server in PolicyLayer and add a rule for report_checkout_fail: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Z Zero. Nothing to install.
report_checkout_fail is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the report_checkout_fail rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for report_checkout_fail. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
report_checkout_fail is provided by the Z Zero MCP server (z-zero-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →