Delete an existing webhook from Fathom. This tool removes a webhook subscription, stopping all future notifications to that endpoint. Args: - id (string, required): The ID of the webhook to delete Returns: Confirmation of successful deletion. Examples: - Delete webhook: { id:
AI agents call fathom_delete_webhook to permanently remove resources in Fathom MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a webhook configuration, which is an irreversible deletion action. While not as severe as deleting actual data (like meetings or transcripts), it destroys integration state that could disrupt monitoring and notification systems. An AI agent could maliciously or accidentally disable critical webhook-based workflows, notification pipelines, or integrations.
From the tool's definition Tool description explicitly states 'Delete an existing webhook' and 'removes a webhook subscription, stopping all future notifications.' The operation is irreversible—once deleted, the webhook configuration cannot be automatically recovered without recreation.
Attacks that exploit this kind of access
Delete an existing webhook from Fathom. This tool removes a webhook subscription, stopping all future notifications to that endpoint. Args: - id (string, required): The ID of the webhook to delete Returns: Confirmation of successful deletion. Examples: - Delete webhook: { id:. It is categorised as a Destructive tool in the Fathom MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fathom MCP Server MCP server in PolicyLayer and add a rule for fathom_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 Fathom MCP Server. Nothing to install.
fathom_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 fathom_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 fathom_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.
fathom_delete_webhook is provided by the Fathom MCP Server MCP server (lukas-bekr/fathom-mcp). 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 →