register_webhook
Register a webhook URL to receive payment notifications. Max 5 webhooks per agent. REQUIRES AGENT KEY.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/register-webhook.md
What register_webhook does on Lightning Wallet
AI agents use register_webhook to create or update resources in Lightning Wallet, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lightning Wallet environment.
Why register_webhook is rated Medium
This tool creates a webhook resource linked to the agent's payment system. While it does not move money (not Financial), does not delete data (not Destructive), and does not execute arbitrary code (not Execute), it does persistently modify the agent's configuration state by adding a callback endpoint.
From the tool's definition Tool description states 'Register a webhook URL' — this creates a new webhook configuration that persists. The action is reversible (webhooks can be deleted/updated), so it is Write rather than Destructive.
Attacks that exploit this kind of access
The rule that runs register_webhook 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 register_webhook, this is the rule to start with:
register_webhook stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 register_webhook call is checked against it from then on.
Questions about register_webhook
Register a webhook URL to receive payment notifications. Max 5 webhooks per agent. REQUIRES AGENT KEY. It is categorised as a Write tool in the Lightning Wallet MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lightning Wallet MCP server in PolicyLayer and add a rule for register_webhook: 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.
register_webhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the register_webhook 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 register_webhook. 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.
register_webhook 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.
This server
Across the catalogue