Get a single-use virtual Visa to make a purchase on behalf of the user. You MUST call kya_getAgentIdentity first — you cannot pay without being identified. Declare the merchant, amount, and what you
AI agents use kya_getCard to commit financial operations through Payclaw — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly creates a financial instrument (virtual Visa card) intended for making purchases. It commits financial obligations on the user's behalf on Visa payment rails. Misuse could result in unauthorized charges, making it Financial category with critical severity due to the direct monetary impact and delegation of spending authority.
From the tool's definition 'Get a single-use virtual Visa to make a purchase on behalf of the user' — explicitly issues a payment instrument (virtual Visa card) to conduct financial transactions on behalf of a user.
Attacks that exploit this kind of access
Get a single-use virtual Visa to make a purchase on behalf of the user. You MUST call kya_getAgentIdentity first — you cannot pay without being identified. Declare the merchant, amount, and what you. It is categorised as a Financial tool in the Payclaw MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Payclaw MCP server in PolicyLayer and add a rule for kya_getCard: 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 Payclaw. Nothing to install.
kya_getCard 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 kya_getCard 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 kya_getCard. 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.
kya_getCard is provided by the Payclaw MCP server (kyalabs-io/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 →