Execute a payment using a temporary token. This tool will securely fill the checkout form on the target website. You will NEVER see the real card number - it is handled securely in the background.
AI agents use execute_payment 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 |
|---|---|---|---|
hints | object | — | Optional hints from get_merchant_hints — selectors and pre-steps to guide Playwright. Use when default selectors fail or for complex multi-step checkouts. |
token | string | Yes | The temporary payment token from request_payment_token |
checkout_url | string | Yes | The full URL of the checkout/payment page |
actual_amount | number | — | The actual final amount on the checkout page. If different from token amount, system will auto-refund the difference. |
Parameters from the server's own tool schema.
This tool executes an actual payment on an external website, committing real funds. It is unambiguously Financial in nature. The severity is critical because an AI agent misusing this tool could trigger unauthorized real-money transactions at arbitrary merchants, with potentially irreversible financial consequences.
From the tool's definition "Execute a payment using a temporary token" and "securely fill the checkout form on the target website" — directly initiates a real financial transaction using a virtual Visa card.
Risk signalsHandles credentials or secrets (token) · High parameter count (12 properties)
Attacks that exploit this kind of access
Execute a payment using a temporary token. This tool will securely fill the checkout form on the target website. You will NEVER see the real card number - it is handled securely in the background. 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.
execute_payment accepts 4 parameters: hints, token, checkout_url, actual_amount. Required: token, 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 execute_payment: 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.
execute_payment 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 execute_payment 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 execute_payment. 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.
execute_payment 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 →