get_fathom_meeting
Get details for a single Fathom meeting by its recording_id. Finds the meeting in your recent history and fetches its AI-generated summary. Returns: - Meeting title, scheduled times, duration - Recording URL and shareable link - Calendar invitees with names/emails - AI-generated summary (if avail...
This record as markdown: /tools/freshdesk/get-fathom-meeting.md
What get_fathom_meeting does on Freshdesk
AI agents call get_fathom_meeting to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_fathom_meeting is rated Low
This tool performs data retrieval only. It queries and returns meeting metadata and summaries from Fathom without any side effects, modifications, or state changes. The blast radius of misuse is minimal—an agent could view meeting information it shouldn't have access to, but cannot alter, delete, or trigger actions. This is a straightforward Read operation.
From the tool's definition Tool retrieves meeting details including 'Meeting title, scheduled times, duration', 'Recording URL', 'Calendar invitees', and 'AI-generated summary'.
Attacks that exploit this kind of access
The rule that runs get_fathom_meeting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_fathom_meeting, this is the rule to start with:
get_fathom_meeting is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every get_fathom_meeting call is checked against it from then on.
Questions about get_fathom_meeting
Get details for a single Fathom meeting by its recording_id. Finds the meeting in your recent history and fetches its AI-generated summary. Returns: - Meeting title, scheduled times, duration - Recording URL and shareable link - Calendar invitees with names/emails - AI-generated summary (if available) Note: Searches through up to 10 pages of recent meetings. For older meetings, use list_fathom_meetings with created_after/created_before date filters first. For transcript content, use get_fathom_transcript separately. Rate limit: May use 1-11 API calls depending on meeting position in history. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for get_fathom_meeting: 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 Freshdesk. Nothing to install.
get_fathom_meeting 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 get_fathom_meeting 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 get_fathom_meeting. 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.
get_fathom_meeting is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue