Publish/deploy the current agent configuration as a new version.
AI agents invoke retell_publish_agent to trigger actions in Retell AI MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Publishing/deploying an agent configuration triggers an external operation that makes the agent live/active in production. This is an Execute-category action as it triggers an external deployment operation with real-world effects (activating an AI phone agent). Severity is high because deploying a misconfigured agent could result in widespread incorrect behavior across all calls handled by that agent.
From the tool's definition Publish/deploy the current agent configuration as a new version
Attacks that exploit this kind of access
Publish/deploy the current agent configuration as a new version. It is categorised as a Execute tool in the Retell AI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Retell AI MCP Server MCP server in PolicyLayer and add a rule for retell_publish_agent: 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 Retell AI MCP Server. Nothing to install.
retell_publish_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the retell_publish_agent 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 retell_publish_agent. 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.
retell_publish_agent is provided by the Retell AI MCP Server MCP server (itsanamune/retellsimp). 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 →