Search across Fathom meeting titles, transcripts, and summaries. This tool performs a text search across your meeting content to find relevant discussions, mentions, or topics. Args: - query (string, required): Search string (2-200 characters) - created_after (string): Filter to meetings after th...
AI agents call fathom_search_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 search/query operation that retrieves and filters existing meeting data without side effects. The tool only reads meeting titles, transcripts, and summaries. Even with broad search capabilities, the blast radius of misuse is limited to information disclosure of meeting content the user has access to, making it a low-severity Read operation.
From the tool's definition Tool performs 'text search across Fathom meeting content' with filtering by date and team. Arguments are all read-only filters (query, created_after, created_before, teams, limit). No modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search across Fathom meeting titles, transcripts, and summaries. This tool performs a text search across your meeting content to find relevant discussions, mentions, or topics. Args: - query (string, required): Search string (2-200 characters) - created_after (string): Filter to meetings after this ISO 8601 timestamp - created_before (string): Filter to meetings before this ISO 8601 timestamp - teams (string[]): Filter by team names - limit (number): Max results to return (1-50, default: 10) - response_format (. 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_search_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_search_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_search_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_search_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_search_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 →