Get analytics about meeting participants and recorders in Fathom. This tool analyzes who attends your meetings most frequently and which domains are most common. Args: - created_after (string): Filter to meetings after this ISO 8601 timestamp - created_before (string): Filter to meetings before t...
AI agents call fathom_participant_stats 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 tool retrieves and analyzes existing meeting analytics data without side effects. It only reads data using standard filter parameters. The sole function is to query and return participant statistics, making it a Read category tool with low severity since misuse would only expose analytics metadata about meeting participants, not enable destructive or financial actions.
From the tool's definition Tool description states it 'Get analytics about meeting participants and recorders' and 'analyzes who attends your meetings most frequently and which domains are most common.' The arguments are all filters and limits for querying existing data (created_after,…
Attacks that exploit this kind of access
Get analytics about meeting participants and recorders in Fathom. This tool analyzes who attends your meetings most frequently and which domains are most common. Args: - created_after (string): Filter to meetings after this ISO 8601 timestamp - created_before (string): Filter to meetings before this ISO 8601 timestamp - limit (number): Max top participants/recorders to return (1-100, 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_participant_stats: 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_participant_stats 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_participant_stats 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_participant_stats. 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_participant_stats 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 →