AI agents use update_retell_llm to create or update resources in Retellai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Retellai environment.
This tool modifies existing Retell LLM configurations reversibly. It is not destructive (no deletion), not financial (no money movement), and not execute (no arbitrary code execution). It fits squarely in Write category. Severity is medium because misconfiguration of LLM parameters could affect call quality or AI behavior, but the change is reversible and the blast radius is limited to that specific LLM instance.
From the tool's definition Tool name 'update_retell_llm' and description 'Updates an existing Retell LLM' indicate modification of data. The verb 'update' is explicitly write-class operation that modifies but does not delete resources.
Attacks that exploit this kind of access
Updates an existing Retell LLM. It is categorised as a Write tool in the Retellai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Retellai MCP server in PolicyLayer and add a rule for update_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 Retellai. Nothing to install.
update_retell_llm is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_retell_llm is provided by the Retellai MCP server (@abhaybabbar/retellai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →