AI agents use pay to commit financial operations through MCP Money — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves money/commits financial obligations by paying Lightning invoices. Lightning payments are irreversible transactions that transfer value. Combined with the Financial category rules (Financial > Destructive > Execute > Write > Read), this is the most severe category. Severity is critical because an AI agent could misuse this to pay arbitrary invoices, potentially draining funds from the account.
From the tool's definition Tool name 'pay' with description 'Pay a Lightning invoice' indicates direct money transfer via Lightning Network payment protocol.
Documented attack patterns abuse exactly the kind of access pay gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Money, and nothing reaches the server without passing your rules. This is the rule we recommend for pay:
{
"version": "1",
"default": "deny",
"tools": {
"pay": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to pay is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Pay a Lightning invoice. It is categorised as a Financial tool in the MCP Money MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MCP Money MCP server in PolicyLayer and add a rule for pay: 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 MCP Money. Nothing to install.
pay 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 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. 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 is provided by the MCP Money MCP server (pablof7z/mcp-money). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Money, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Money tools catalogued and risk-classified — across an index of 43,000+ MCP servers.