list_fathom_teams
List all teams accessible to the user in Fathom. Returns teams with: - name: Team name (use for filtering meetings or listing members) - created_at: When the team was created (if available) Use this to find team names for filtering meetings with list_fathom_meetings or listing team members with l...
This record as markdown: /tools/freshdesk/list-fathom-teams.md
What list_fathom_teams does on Freshdesk
AI agents call list_fathom_teams 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_teams is rated Low
This tool retrieves team metadata from Fathom without modifying, deleting, or executing any operations. It is a straightforward data query operation that falls squarely into the Read category. The low severity reflects that exposing a list of team names and creation dates has minimal blast radius—it reveals organizational structure but enables no destructive or financial actions.
From the tool's definition Tool description states it 'List all teams' and 'Returns teams with: name, created_at'. The verb 'list' is explicitly read-only retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs list_fathom_teams 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_teams, this is the rule to start with:
list_fathom_teams 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_teams call is checked against it from then on.
Questions about list_fathom_teams
List all teams accessible to the user in Fathom. Returns teams with: - name: Team name (use for filtering meetings or listing members) - created_at: When the team was created (if available) Use this to find team names for filtering meetings with list_fathom_meetings or listing team members with list_fathom_team_members. 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_teams: 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_teams 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_teams 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_teams. 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_teams 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