transfer_to_agent
Transfer sats between agents or from operator to agent. REQUIRES OPERATOR KEY.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/transfer-to-agent.md
What transfer_to_agent does on Lightning Wallet
AI agents use transfer_to_agent to commit financial operations through Lightning Wallet, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why transfer_to_agent is rated Critical
This tool directly transfers monetary value (Bitcoin satoshis) from one party to another. It is a financial transaction that commits cryptocurrency obligations and moves money. The 'REQUIRES OPERATOR KEY' note indicates it is a privileged operation with clear authorization semantics. Misuse by an AI agent could result in unauthorized cryptocurrency transfers, making it the highest severity risk.
From the tool's definition Tool name is 'transfer_to_agent' and description states 'Transfer sats between agents or from operator to agent.' Sats are satoshis, the smallest unit of Bitcoin. The tool moves cryptocurrency value between parties.
Attacks that exploit this kind of access
The rule that runs transfer_to_agent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lightning Wallet, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_to_agent, this is the rule to start with:
Any call to transfer_to_agent is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Lightning Wallet, apply this rule, and every transfer_to_agent call is checked against it from then on.
Questions about transfer_to_agent
Transfer sats between agents or from operator to agent. REQUIRES OPERATOR KEY. It is categorised as a Financial tool in the Lightning Wallet MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Lightning Wallet MCP server in PolicyLayer and add a rule for transfer_to_agent: 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 Lightning Wallet. Nothing to install.
transfer_to_agent 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 transfer_to_agent 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 transfer_to_agent. 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.
transfer_to_agent is provided by the Lightning Wallet MCP server (lightning-wallet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lightning Wallet, and thousands of servers like it.
Across the catalogue