get_card_details

Get PAN, CVV, and expiry for a card. This is audit-logged.

SERVERAgentpay SOURCEagentpay-mcp-server
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/agentpay/get-card-details.md

What get_card_details does on Agentpay

AI agents call get_card_details to retrieve information from Agentpay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
card_id string Yes Card ID

Parameters from the server's own tool schema.

Why get_card_details is rated Low

This tool retrieves sensitive financial data (PAN, CVV, expiry) but does not create, modify, delete, or move money. It is a Read operation accessing highly sensitive payment card information. High severity reflects that exposing this data could lead to fraud or unauthorized card use, despite being read-only. Audit-logging mitigates some risk but does not change the operation category.

From the tool's definition Tool name explicitly 'get_card_details' and description states it retrieves 'PAN, CVV, and expiry' — sensitive payment card data. The phrase 'Get' and 'for a card' confirms read-only retrieval operation.

Questions about get_card_details

What does the get_card_details tool do? +

Get PAN, CVV, and expiry for a card. This is audit-logged. It is categorised as a Read tool in the Agentpay MCP Server, which means it retrieves data without modifying state.

What parameters does get_card_details accept? +

get_card_details accepts 1 parameter: card_id. Required: card_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_card_details? +

Register the Agentpay MCP server in PolicyLayer and add a rule for get_card_details: 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.

What risk level is get_card_details? +

get_card_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_card_details? +

Yes. Add a rate_limit block to the get_card_details 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.

How do I block get_card_details completely? +

Set action: deny in the PolicyLayer policy for get_card_details. 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.

What MCP server provides get_card_details? +

get_card_details 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Agentpay's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.