Create a deposit invoice (bolt11) for the specified amount and mint. Returns the invoice immediately for payment. If no mint is specified, all mints will be tried concurrently and the first successful response will be used.
AI agents use deposit to commit financial operations through MCP Money — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The deposit tool commits financial obligations by creating invoices that enable payment processing. It directly handles monetary transfers via Lightning Network (bolt11 invoices) and Cashu, which are financial systems. An AI agent misusing this could initiate unauthorized deposits or financial commitments.
From the tool's definition Tool creates a deposit invoice (bolt11) for specified amount and mint, enabling monetary transactions. Server description explicitly states 'money functionalities' and sibling tools include 'pay' and 'zap' which are financial operations.
Documented attack patterns abuse exactly the kind of access deposit 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 deposit:
{
"version": "1",
"default": "deny",
"tools": {
"deposit": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to deposit is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create a deposit invoice (bolt11) for the specified amount and mint. Returns the invoice immediately for payment. If no mint is specified, all mints will be tried concurrently and the first successful response will be used. 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 deposit: 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.
deposit 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 deposit 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 deposit. 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.
deposit 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.