List meetings from Fathom with optional filtering and pagination. This tool retrieves meeting recordings from your Fathom account. You can filter by: - Company domains of calendar invitees - Internal vs external meetings - Date range (created_after/created_before) - Recorder email addresses - Tea...
AI agents call fathom_list_meetings to retrieve information from Fathom MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval tool that queries and filters existing meeting data. While it can return sensitive information (transcripts, summaries, CRM data), it performs no side effects, making it clearly a Read operation.
From the tool's definition Tool 'retrieves meeting recordings from your Fathom account' with optional filtering by domains, dates, recorder emails, and team names.
Attacks that exploit this kind of access
List meetings from Fathom with optional filtering and pagination. This tool retrieves meeting recordings from your Fathom account. You can filter by: - Company domains of calendar invitees - Internal vs external meetings - Date range (created_after/created_before) - Recorder email addresses - Team names You can optionally include: - AI-generated summaries - Full transcripts - Action items - CRM matches (contacts, companies, deals) Args: - calendar_invitees_domains (string[]): Filter by company domains - calendar_invitees_domains_type (. It is categorised as a Read tool in the Fathom MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fathom MCP Server MCP server in PolicyLayer and add a rule for fathom_list_meetings: 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_list_meetings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fathom_list_meetings 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_list_meetings. 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_list_meetings 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 →