Delete a webhook
AI agents call delete-webhook to permanently remove resources in ClickUp Operator — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a webhook is a destructive operation that cannot be undone without manual reconfiguration. The webhook deletion removes an integration point and its associated event routing, which is an irreversible action. Severity is high because misconfiguring which webhook to delete could break important automated workflows or integrations in ClickUp, affecting multiple tasks and processes.
From the tool's definition Tool name is 'delete-webhook' with description 'Delete a webhook'. The verb 'delete' is explicit and indicates irreversible removal of a webhook configuration.
Attacks that exploit this kind of access
Delete a webhook. It is categorised as a Destructive tool in the ClickUp Operator MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ClickUp Operator 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 ClickUp Operator. 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 ClickUp Operator MCP server (noah-vh/mcp-server-clickup). 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 →