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 ...
AI agents call list_fathom_meetings to retrieve information from Apple Shortcuts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read operation that retrieves meeting metadata from Fathom. It has no side effects and does not modify, delete, or execute operations. Severity is medium rather than low because the tool exposes sensitive meeting information including attendee lists with names/emails and recording identifiers, which could be misused for reconnaissance or privacy violations if an AI agent indiscriminately queries meetings…
From the tool's definition Tool description states 'List meetings from Fathom' and 'Returns meeting metadata including: recording_id, title, scheduled_start_time, duration, calendar_invitees, teams'.
Documented attack patterns abuse exactly the kind of access list_fathom_meetings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Shortcuts, and nothing reaches the server without passing your rules. This is the rule we recommend for list_fathom_meetings:
{
"version": "1",
"default": "deny",
"tools": {
"list_fathom_meetings": {}
}
}list_fathom_meetings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 Apple Shortcuts MCP Server, which means it retrieves data without modifying state.
Register the Apple Shortcuts 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 Apple Shortcuts. 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 Apple Shortcuts MCP server (@mindstone/mcp-server-apple-shortcuts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apple Shortcuts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
423 Apple Shortcuts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.