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.

SERVERLightning Wallet SOURCElightning-wallet-mcp
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about nostr_zap

What does the nostr_zap tool do? +

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.

How do I enforce a policy on nostr_zap? +

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.

What risk level is nostr_zap? +

nostr_zap is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit nostr_zap? +

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.

How do I block nostr_zap completely? +

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.

What MCP server provides nostr_zap? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Lightning Wallet's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.