list_chats
List recent Teams chats (1:1, group, and meeting chats).
This record as markdown: /tools/freshdesk/list-chats.md
What list_chats does on Freshdesk
AI agents call list_chats 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_chats is rated Low
The tool queries and returns a list of existing chat data without creating, modifying, deleting, or executing any actions. This is a straightforward read operation with minimal risk—listing chat metadata does not alter system state or expose sensitive conversation contents beyond normal user permissions.
From the tool's definition Tool name 'list_chats' and description 'List recent Teams chats' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_chats 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_chats, this is the rule to start with:
list_chats 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_chats call is checked against it from then on.
Questions about list_chats
List recent Teams chats (1:1, group, and meeting chats). 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_chats: 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_chats 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_chats 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_chats. 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_chats 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