lightning_fund_from_btc
Fund the Lightning wallet from the user
This record as markdown: /tools/io-github-aibtcdev-mcp-server/lightning-fund-from-btc.md
What lightning_fund_from_btc does on Aibtc
AI agents use lightning_fund_from_btc to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why lightning_fund_from_btc is rated Critical
This tool moves actual Bitcoin funds from a user into a Lightning wallet, constituting a real financial transaction. Combined with sibling tools like alex_swap and bitflow_create_order that confirm this is a financial/crypto trading server, misuse could result in unauthorized fund transfers. Severity is critical due to irreversible nature of cryptocurrency transactions.
From the tool's definition Fund the Lightning wallet from the user
Attacks that exploit this kind of access
The rule that runs lightning_fund_from_btc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lightning_fund_from_btc, this is the rule to start with:
Any call to lightning_fund_from_btc is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every lightning_fund_from_btc call is checked against it from then on.
Questions about lightning_fund_from_btc
Fund the Lightning wallet from the user. It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for lightning_fund_from_btc: 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 Aibtc. Nothing to install.
lightning_fund_from_btc 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 lightning_fund_from_btc 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 lightning_fund_from_btc. 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.
lightning_fund_from_btc is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
Across the catalogue