This record as markdown: /tools/io-github-pay-skill-pay-mcp/pay-webhook-delete.md
What pay_webhook_delete does on Pay Mcp
AI agents call pay_webhook_delete to permanently remove resources in Pay Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why pay_webhook_delete is rated Critical
This tool deletes a webhook registration, which is an irreversible destructive action. In the context of a payment server handling USDC transactions on Base, removing a webhook could silently disable payment notifications and event callbacks, potentially causing missed payment events or disrupting financial workflows.
From the tool's definition 'Delete a webhook registration by its ID' — permanently removes a webhook registration, which is an irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs pay_webhook_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pay Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pay_webhook_delete, this is the rule to start with:
pay_webhook_delete 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 Pay Mcp, apply this rule, and every pay_webhook_delete call is checked against it from then on.
Questions about pay_webhook_delete
Delete a webhook registration by its ID. It is categorised as a Destructive tool in the Pay Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pay MCP server in PolicyLayer and add a rule for pay_webhook_delete: 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 Pay Mcp. Nothing to install.
pay_webhook_delete 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 pay_webhook_delete 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 pay_webhook_delete. 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.
pay_webhook_delete is provided by the Pay MCP server (@pay-skill/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pay, and thousands of servers like it.
Across the catalogue