lnurl_auth
Authenticate to a service using LNURL-auth protocol. REQUIRES AGENT KEY.
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
Attacks that exploit this kind of access
The rule that runs lnurl_auth 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 lnurl_auth, this is the rule to start with:
lnurl_auth stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Lightning Wallet, apply this rule, and every lnurl_auth call is checked against it from then on.
Questions about lnurl_auth
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.
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.
lnurl_auth is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
Across the catalogue