get_retell_llm
Get details of a Retell LLM response engine (prompt, model, tools). WHEN TO USE: - Inspect current prompt/model before update_retell_llm - Confirm which prompt an agent will use before a call - Debug why an agent said the wrong thing COMMON MISTAKES: - Looking at the agent only; the actual call i...
This record as markdown: /tools/freshdesk/get-retell-llm.md
What get_retell_llm does on Freshdesk
AI agents call get_retell_llm 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 get_retell_llm is rated Low
This tool retrieves and inspects details about an existing Retell LLM configuration (prompt, model, tools). It has no side effects and performs only data retrieval. The documented use cases confirm it is diagnostic/informational in nature. Severity is low because inspection of configuration data poses minimal risk compared to tools that execute, modify, or delete resources.
From the tool's definition The tool name is 'get_retell_llm' and the description explicitly states it is used to 'Get details of a Retell LLM response engine' with use cases such as 'Inspect current prompt/model', 'Confirm which prompt', and 'Debug'.
Attacks that exploit this kind of access
The rule that runs get_retell_llm 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 get_retell_llm, this is the rule to start with:
get_retell_llm 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 get_retell_llm call is checked against it from then on.
Questions about get_retell_llm
Get details of a Retell LLM response engine (prompt, model, tools). WHEN TO USE: - Inspect current prompt/model before update_retell_llm - Confirm which prompt an agent will use before a call - Debug why an agent said the wrong thing COMMON MISTAKES: - Looking at the agent only; the actual call instructions live in the Retell LLM - Editing a different LLM than the one returned by get_agent.response_engine.llm_id ERROR RECOVERY: - 401: API key is missing or invalid → configure_retell_api_key - 404: llm_id not found → get_agent/list_retell_llms and retry RELATED TOOLS: - get_agent: Find response_engine.llm_id for an agent - update_retell_llm: Change the prompt/model - list_retell_llms: Browse available LLM configs RETURNS: llm_id, general_prompt, begin_message, model, model_temperature, general_tools, 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 get_retell_llm: 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.
get_retell_llm 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 get_retell_llm 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 get_retell_llm. 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.
get_retell_llm 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