Deletes a phone number
AI agents call delete_phone_number to permanently remove resources in Retellai — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a phone number is an irreversible action that cannot be undone. Once deleted, the phone number resource is permanently removed from the system. This meets the definition of Destructive (irreversibly deletes data). While the blast radius is not as severe as deleting agents or calls (which might affect active operations), it is still a significant destructive action warranting 'high' severity.
From the tool's definition Tool name is 'delete_phone_number' and description states 'Deletes a phone number'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Deletes a phone number. It is categorised as a Destructive tool in the Retellai MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Retellai MCP server in PolicyLayer and add a rule for delete_phone_number: 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.
delete_phone_number is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_phone_number 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 delete_phone_number. 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.
delete_phone_number 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 →