List members of a specific team or all teams in Fathom. This tool retrieves team member information including names, emails, and when they joined. Args: - team (string): Filter by team name (optional - shows all members if not specified) - cursor (string): Pagination cursor from previous response...
AI agents call fathom_list_team_members 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 only retrieves and queries team member data with no side effects. It is purely informational (list/get operation) and does not create, modify, delete, or execute any actions. The low severity reflects minimal risk even if misused—an AI agent can only read existing team membership data, which is typically non-sensitive or already accessible within an organization.
From the tool's definition Tool name 'fathom_list_team_members' and description 'List members of a specific team or all teams in Fathom' with functionality to 'retrieve team member information including names, emails, and when they joined.' No modification, deletion, or execution…
Attacks that exploit this kind of access
List members of a specific team or all teams in Fathom. This tool retrieves team member information including names, emails, and when they joined. Args: - team (string): Filter by team name (optional - shows all members if not specified) - cursor (string): Pagination cursor from previous response - 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_list_team_members: 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_list_team_members 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_list_team_members 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_list_team_members. 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_list_team_members 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 →