lnurl_auth

Authenticate to a service using LNURL-auth protocol. REQUIRES AGENT KEY.

SERVERLightning Wallet SOURCElightning-wallet-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/lnurl-auth.md

What lnurl_auth does on Lightning Wallet

AI agents invoke lnurl_auth to trigger actions in Lightning Wallet. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why lnurl_auth is rated High

LNURL-auth triggers an external cryptographic authentication operation against a third-party service using the agent's key. It is not a simple data read — it performs an active external operation (signing and sending an authentication request) that establishes a session or identity claim on a remote service. This falls under Execute as it triggers external operations whose effects depend on arguments.

From the tool's definition Authenticate to a service using LNURL-auth protocol

Questions about lnurl_auth

What does the lnurl_auth tool do? +

Authenticate to a service using LNURL-auth protocol. REQUIRES AGENT KEY. It is categorised as a Execute tool in the Lightning Wallet MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lnurl_auth? +

Register the Lightning Wallet MCP server in PolicyLayer and add a rule for lnurl_auth: 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 lnurl_auth? +

lnurl_auth is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit lnurl_auth? +

Yes. Add a rate_limit block to the lnurl_auth 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 lnurl_auth completely? +

Set action: deny in the PolicyLayer policy for lnurl_auth. 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 lnurl_auth? +

lnurl_auth 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.