nostr_zap
Send a Nostr zap (NIP-57 Lightning payment with optional Nostr event). If the recipient supports NIP-57, a proper zap receipt is created. Otherwise falls back to a regular Lightning address payment. REQUIRES AGENT KEY with Nostr identity set.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/nostr-zap.md
What nostr_zap does on Lightning Wallet
AI agents use nostr_zap to commit financial operations through Lightning Wallet, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why nostr_zap is rated Critical
This tool sends actual Bitcoin payments over the Lightning Network. It moves real funds from the agent's wallet to a recipient, constituting a direct financial transaction. Misuse could drain the wallet balance irreversibly, warranting critical severity.
From the tool's definition Send a Nostr zap (NIP-57 Lightning payment with optional Nostr event)... falls back to a regular Lightning address payment
Attacks that exploit this kind of access
The rule that runs nostr_zap 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 nostr_zap, this is the rule to start with:
Any call to nostr_zap 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 nostr_zap call is checked against it from then on.
Questions about nostr_zap
Send a Nostr zap (NIP-57 Lightning payment with optional Nostr event). If the recipient supports NIP-57, a proper zap receipt is created. Otherwise falls back to a regular Lightning address payment. REQUIRES AGENT KEY with Nostr identity set. 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 nostr_zap: 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.
nostr_zap 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 nostr_zap 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 nostr_zap. 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.
nostr_zap 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