This record as markdown: /tools/com-quintadb-mcp/delete-webhook.md
What delete_webhook does on QuintaDB
AI agents call delete_webhook to permanently remove resources in QuintaDB, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
webhook_id | string | Yes | Webhook ID (from list_webhooks) |
Parameters from the server's own tool schema.
Why delete_webhook is rated Critical
Deleting a webhook irreversibly removes an integration point and its configuration. This cannot be undone without manual recreation. While the blast radius is limited to webhook infrastructure rather than data records, it is destructive by nature and ranks above Write/Execute due to its irreversible effect on system state.
From the tool's definition Tool name 'delete_webhook' and description 'Видалити вебхук' (Ukrainian for 'Delete webhook') indicate permanent removal of a webhook configuration.
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 QuintaDB, 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 QuintaDB, apply this rule, and every delete_webhook call is checked against it from then on.
Questions about delete_webhook
Видалити вебхук. It is categorised as a Destructive tool in the QuintaDB MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_webhook accepts 2 parameters: app_id, webhook_id. Required: app_id, webhook_id. The full parameter table on this page comes from the server's own tool schema.
Register the QuintaDB 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 QuintaDB. 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 QuintaDB MCP server (https://quintadb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on QuintaDB, and thousands of servers like it.
Across the catalogue