delete_webhook
Delete a registered webhook. REQUIRES AGENT KEY.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/delete-webhook.md
What delete_webhook does on Lightning Wallet
AI agents call delete_webhook to permanently remove resources in Lightning Wallet, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_webhook is rated Critical
Deleting a webhook is an irreversible action that removes a configured integration endpoint. While it doesn't move money directly, it could disrupt payment notifications and L402 callbacks, potentially causing financial or operational issues. Classified as Destructive due to the permanent removal of a registered resource.
From the tool's definition "Delete a registered webhook" — permanently removes a registered webhook integration
Attacks that exploit this kind of access
The rule that runs delete_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 delete_webhook, this is the rule to start with:
delete_webhook is removed from the agent's tool list entirely, so the agent never calls 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 delete_webhook call is checked against it from then on.
Questions about delete_webhook
Delete a registered webhook. REQUIRES AGENT KEY. It is categorised as a Destructive tool in the Lightning Wallet MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lightning Wallet MCP server in PolicyLayer and add a rule for delete_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.
delete_webhook is a Destructive 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 delete_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 delete_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.
delete_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.
Across the catalogue