AI agents use update_phone_number to create or update resources in Telnyx MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telnyx MCP Server environment.
This is a Write operation because it modifies existing data reversibly. Severity is high rather than medium because phone number configuration changes in a telephony platform directly affect call routing, messaging delivery, and business communications, creating substantial blast radius if misconfigured by an agent.
From the tool's definition Tool name is 'update_phone_number' and description states 'Update a phone number.' The verb 'update' indicates modification of existing data.
Documented attack patterns abuse exactly the kind of access update_phone_number gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telnyx MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_phone_number:
{
"version": "1",
"default": "deny",
"tools": {
"update_phone_number": {
"limits": [
{
"counter": "update_phone_number_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_phone_number stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update a phone number. It is categorised as a Write tool in the Telnyx MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telnyx MCP Server MCP server in PolicyLayer and add a rule for update_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 Telnyx MCP Server. Nothing to install.
update_phone_number 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_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 update_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.
update_phone_number is provided by the Telnyx MCP Server MCP server (team-telnyx/telnyx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telnyx MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
46 Telnyx MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.