create_card
Create a single-use virtual card for a purchase. Use guard:true for autonomous purchases (15-min expiry).
This record as markdown: /tools/agentpay/create-card.md
What create_card does on Agentpay
AI agents use create_card to commit financial operations through Agentpay, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
guard | boolean | — | Spending guard: 15-min expiry, velocity limited |
amount | number | Yes | Amount in currency units (e.g. 25.00) |
context | string | — | Why you need this card (shown in approval notification) |
currency | string | Yes | Currency code (usd, clp, brl, mxn) |
merchant_lock | string | — | Restrict to this merchant |
Parameters from the server's own tool schema.
Why create_card is rated Critical
This tool creates a virtual payment card for making purchases, directly committing financial resources. Misuse by an AI agent could result in unauthorized financial transactions. The 'autonomous purchases' feature makes this especially high-risk as it enables unsupervised spending.
From the tool's definition Create a single-use virtual card for a purchase... autonomous purchases (15-min expiry)
Attacks that exploit this kind of access
The rule that runs create_card safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentpay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_card, this is the rule to start with:
Any call to create_card is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Agentpay, apply this rule, and every create_card call is checked against it from then on.
Questions about create_card
Create a single-use virtual card for a purchase. Use guard:true for autonomous purchases (15-min expiry). It is categorised as a Financial tool in the Agentpay MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
create_card accepts 5 parameters: guard, amount, context, currency, merchant_lock. Required: amount, currency. The full parameter table on this page comes from the server's own tool schema.
Register the Agentpay MCP server in PolicyLayer and add a rule for create_card: 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 Agentpay. Nothing to install.
create_card 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 create_card 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 create_card. 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.
create_card is provided by the Agentpay MCP server (agentpay-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentpay, and thousands of servers like it.
Across the catalogue