Register an inbound call from a custom telephony provider.
AI agents invoke retell_register_phone_call 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.
This tool triggers an external telephony operation — registering/initiating an inbound call — which causes real-world side effects beyond simple data creation. It interacts with live phone infrastructure and could result in active voice calls being established. This goes beyond a Write (data creation) into Execute territory since it triggers external operational processes in a telephony system.
From the tool's definition Register an inbound call from a custom telephony provider
Attacks that exploit this kind of access
Register an inbound call from a custom telephony provider. 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_register_phone_call: 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_register_phone_call 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_register_phone_call 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_register_phone_call. 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_register_phone_call 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 →