list_teams
List Teams you are a member of.
This record as markdown: /tools/freshdesk/list-teams.md
What list_teams does on Freshdesk
AI agents call list_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_teams is rated Low
This tool retrieves and queries data (team membership) with no side effects. It performs a straightforward list/fetch operation typical of Read category tools. The low severity reflects minimal blast radius—an AI agent can only discover teams the user belongs to, with no ability to modify, delete, or trigger external operations.
From the tool's definition Tool name is 'list_teams' and description states 'List Teams you are a member of' — a read-only query operation that retrieves membership information without modification.
Attacks that exploit this kind of access
The rule that runs list_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_teams, this is the rule to start with:
list_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_teams call is checked against it from then on.
Questions about list_teams
List Teams you are a member of. 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_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_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_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_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_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