⚠️ MANDATORY: Read mcp://resources/sop first. Only use on PAYMENT pages where final total is visible. Auto-detects Web3 or Fiat and completes payment. For physical goods (Shopify, Etsy), get_merchant_hints first.
AI agents use auto_pay_checkout to commit financial operations through Z Zero — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
card_alias | string | Yes | Card alias to charge for JIT Fiat fallback, e.g. 'Card_01'. |
checkout_url | string | Yes | Full URL of the checkout/payment page to analyze and pay. |
Parameters from the server's own tool schema.
This tool directly executes financial transactions by automatically completing payments on behalf of an AI agent. It commits financial obligations (charges to payment methods) based on agent decisions, which is the defining characteristic of the Financial category.
From the tool's definition Tool name 'auto_pay_checkout' + description explicitly states it 'completes payment' and 'Auto-detects Web3 or Fiat and completes payment.' Server description confirms this is for 'Secure JIT Virtual Card Payment tools' that facilitate actual financial…
Attacks that exploit this kind of access
⚠️ MANDATORY: Read mcp://resources/sop first. Only use on PAYMENT pages where final total is visible. Auto-detects Web3 or Fiat and completes payment. For physical goods (Shopify, Etsy), get_merchant_hints first. It is categorised as a Financial tool in the Z Zero MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
auto_pay_checkout accepts 2 parameters: card_alias, checkout_url. Required: card_alias, checkout_url. 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 auto_pay_checkout: 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.
auto_pay_checkout is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the auto_pay_checkout 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 auto_pay_checkout. 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.
auto_pay_checkout 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 →