Delete a webhook endpoint and all its delivery logs. The endpoint will stop receiving events immediately.
AI agents call delete_webhook to permanently remove resources in QR for Agent — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
webhook_id | number | Yes | The ID of the webhook to delete. Use list_webhooks to find IDs. |
Parameters from the server's own tool schema.
This tool permanently removes webhook configuration and associated delivery history without the ability to recover them. Deletion is irreversible and represents data loss. While not directly financial or involving bulk user data, the removal of a critical integration point and audit trail qualifies as destructive.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a webhook endpoint and all its delivery logs' — both the endpoint configuration and historical logs are irreversibly removed ('will stop receiving events immediately').
Attacks that exploit this kind of access
Delete a webhook endpoint and all its delivery logs. The endpoint will stop receiving events immediately. It is categorised as a Destructive tool in the QR for Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_webhook accepts 1 parameter: webhook_id. Required: webhook_id. The full parameter table on this page comes from the server's own tool schema.
Register the QR for Agent 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 QR for Agent. 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 QR for Agent MCP server (qr-for-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →