list_agents
List all configured voice agents in your Retell account. WHEN TO USE: - Discover available agents before making calls - Find agent IDs by name - Inventory check COMMON MISTAKES: - Guessing agent IDs from names; use the returned agent_id exactly - Choosing an agent without checking its response_en...
This record as markdown: /tools/freshdesk/list-agents.md
What list_agents does on Freshdesk
AI agents call list_agents 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_agents is rated Low
This tool retrieves and queries configuration data about voice agents without side effects. It is a simple inventory/discovery operation that returns information to inform subsequent actions. The related tools (get_agent, create_phone_call) are separate and handle more sensitive operations.
From the tool's definition Tool description states 'List all configured voice agents in your Retell account' and use cases include 'Discover available agents', 'Find agent IDs by name', and 'Inventory check'. No data modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
The rule that runs list_agents 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_agents, this is the rule to start with:
list_agents 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_agents call is checked against it from then on.
Questions about list_agents
List all configured voice agents in your Retell account. WHEN TO USE: - Discover available agents before making calls - Find agent IDs by name - Inventory check COMMON MISTAKES: - Guessing agent IDs from names; use the returned agent_id exactly - Choosing an agent without checking its response_engine.llm_id and versions via get_agent ERROR RECOVERY: - 401: API key is missing or invalid → configure_retell_api_key RELATED TOOLS: - get_agent: Inspect full config for a returned agent_id - get_agent_versions: Check published versions - create_phone_call/create_web_call: Use a verified agent_id RETURNS: agents, count. Each agent usually includes agent_id, agent_name, voice_id, response_engine, and timestamps. 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_agents: 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_agents 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_agents 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_agents. 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_agents 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