AI agents use pay_with_token to commit financial operations through Vnpay — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves money by processing a payment transaction using a tokenized card. It commits a financial obligation (charge to a stored payment method) with real monetary consequences. Financial category supersedes all others; critical severity due to potential for unauthorized charges, fraud, or significant financial loss if an AI agent misuses this without proper authorization controls.
From the tool's definition Tool description states 'Pay using a stored card token' on a payment gateway server (VNPay). The sibling tools include 'refund' and 'create_token', confirming this server handles financial transactions.
Attacks that exploit this kind of access
Pay using a stored card token. It is categorised as a Financial tool in the Vnpay MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Vnpay MCP server in PolicyLayer and add a rule for pay_with_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 Vnpay. Nothing to install.
pay_with_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 pay_with_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 pay_with_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.
pay_with_token is provided by the Vnpay MCP server (theyahia/vnpay-mcp). 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 →