close_card
Close a card and release unused funds. Always call this after a purchase.
This record as markdown: /tools/agentpay/close-card.md
What close_card does on Agentpay
AI agents call close_card to permanently remove resources in Agentpay, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
card_id | string | Yes | Card ID |
Parameters from the server's own tool schema.
Why close_card is rated Critical
Closing a card is a one-way, irreversible operation: once closed, the card cannot be re-opened or restored. This irreversibility places it firmly in the Destructive category. The severity is high because misuse by an AI agent could prematurely terminate a payment instrument mid-transaction, cause loss of card funds, or disrupt financial workflows across multiple operations.
From the tool's definition 'Close a card and release unused funds' — closing a card is an irreversible action that permanently deactivates the card and releases its associated funds.
Attacks that exploit this kind of access
The rule that runs close_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 close_card, this is the rule to start with:
close_card is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Agentpay, apply this rule, and every close_card call is checked against it from then on.
Questions about close_card
Close a card and release unused funds. Always call this after a purchase. It is categorised as a Destructive tool in the Agentpay MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
close_card accepts 1 parameter: card_id. Required: card_id. 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 close_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.
close_card is a Destructive 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 close_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 close_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.
close_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