Create a webhook to receive real-time notifications when meetings are processed in Fathom. This tool creates a webhook subscription that will POST meeting data to your specified URL whenever new meeting content becomes available. Args: - destination_url (string, required): The URL to receive webh...
AI agents use fathom_create_webhook to create or update resources in Fathom MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fathom MCP Server environment.
This tool creates a new configuration entry (webhook subscription) in the Fathom system, which is a reversible Write operation. The severity is medium because: (1) it could enable data exfiltration if a malicious URL is registered to receive meeting transcripts and summaries, and (2) webhooks can generate persistent side effects by automatically sending data to external endpoints.
From the tool's definition Tool description states 'Create a webhook' and 'will POST meeting data to your specified URL' — this creates a new webhook subscription that modifies system state by registering a notification endpoint.
Attacks that exploit this kind of access
Create a webhook to receive real-time notifications when meetings are processed in Fathom. This tool creates a webhook subscription that will POST meeting data to your specified URL whenever new meeting content becomes available. Args: - destination_url (string, required): The URL to receive webhook notifications - triggered_for (string[], required): At least one trigger type: -. It is categorised as a Write tool in the Fathom MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fathom MCP Server MCP server in PolicyLayer and add a rule for fathom_create_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_create_webhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fathom_create_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_create_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_create_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 →