AI agents use request_payment_token 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 |
|---|---|---|---|
amount | number | Yes | Amount in USD to authorize (min: $1, max: $100) |
merchant | string | Yes | Name or URL of the merchant/service being purchased |
card_alias | string | Yes | Which card to charge, e.g. 'Card_01' |
Parameters from the server's own tool schema.
This tool initiates the creation of a Just-In-Time virtual payment card, which is a precursor to committing real financial obligations. Even though it is a 'token request' step, it directly enables real monetary transactions (Visa cards up to $100), placing it firmly in the Financial category.
From the tool's definition Request a JIT virtual card ($1-$100); references 'Secure JIT Virtual Card Payment tools'; siblings include 'execute_payment' and 'auto_pay_checkout' confirming financial transaction context
Attacks that exploit this kind of access
⚠️ MANDATORY: Read mcp://resources/sop first. Collect shipping info and check get_merchant_hints before calling. Request a JIT virtual card ($1-$100). 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.
request_payment_token accepts 3 parameters: amount, merchant, card_alias. Required: amount, merchant, card_alias. 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 request_payment_token: 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.
request_payment_token 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 request_payment_token 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 request_payment_token. 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.
request_payment_token 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 →