list_fathom_meetings
List meetings from Fathom with server-side filtering. Returns meeting metadata including: - recording_id: Primary identifier for get_fathom_meeting and get_fathom_transcript - title, scheduled_start_time, duration - calendar_invitees: Array of attendees with name/email - teams: Teams the meeting ...
This record as markdown: /tools/freshdesk/list-fathom-meetings.md
What list_fathom_meetings does on Freshdesk
AI agents call list_fathom_meetings 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 list_fathom_meetings is rated Low
This is a straightforward data retrieval tool that queries and returns meeting metadata with optional filtering. It has no side effects—it only retrieves and presents existing data without modifying, deleting, or executing any operations. The filtering mechanisms are read-only query parameters that constrain the result set.
From the tool's definition Tool description explicitly states 'List meetings from Fathom' and 'Returns meeting metadata including: recording_id, title, scheduled_start_time, duration, calendar_invitees'.
Attacks that exploit this kind of access
The rule that runs list_fathom_meetings 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 list_fathom_meetings, this is the rule to start with:
list_fathom_meetings 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 list_fathom_meetings call is checked against it from then on.
Questions about list_fathom_meetings
List meetings from Fathom with server-side filtering. Returns meeting metadata including: - recording_id: Primary identifier for get_fathom_meeting and get_fathom_transcript - title, scheduled_start_time, duration - calendar_invitees: Array of attendees with name/email - teams: Teams the meeting belongs to Server-side filters (use these to narrow results efficiently): - teams: Filter by team names - recorded_by: Filter by recorder email addresses - calendar_invitees_domains: Filter by attendee email domains (e.g., find all meetings with acme.com) - meeting_type:. 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 list_fathom_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 Freshdesk. Nothing to install.
list_fathom_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 list_fathom_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 list_fathom_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.
list_fathom_meetings 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