AI agents use create_payment to commit financial operations through Paymongo — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool performs irreversible financial transactions by charging a payment source, committing real monetary transfers. Financial transactions represent the highest severity risk category due to direct potential for unauthorized fund transfers, fraudulent charges, or financial loss. The critical severity reflects that a single misuse could result in substantial monetary harm with no undo capability.
From the tool's definition Tool description explicitly states 'Charge a chargeable source to create a payment (moves money).' The phrase 'moves money' directly indicates financial transaction capability.
Attacks that exploit this kind of access
Charge a chargeable source to create a payment (moves money). It is categorised as a Financial tool in the Paymongo MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Paymongo MCP server in PolicyLayer and add a rule for create_payment: 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 Paymongo. Nothing to install.
create_payment 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_payment 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_payment. 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_payment is provided by the Paymongo MCP server (theyahia/paymongo-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 →