This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/create-phone-number-route.md
What create_phone_number_route does on Elevenlabs
AI agents use create_phone_number_route to create or update resources in Elevenlabs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Elevenlabs environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
sid | string | — | Twilio Account SID (starts with `AC`) or API Key SID (starts with `SK`) |
label | string | — | Label for the phone number |
token | string | — | Secret paired with `sid`: the Account Auth Token for an Account SID, or the API Key Secret for an API Key SID |
app_id | string | — | Exotel applet identifier used in Calls/connect |
api_key | string | — | Exotel API Key |
agent_id | string | null | — | |
provider | string | — | |
api_token | string | — | Exotel API Token |
applet_url | string | null | — | |
enable_sms | boolean | — | Route inbound SMS to ElevenLabs. On by default; set to false to skip SMS configuration for numbers that don't support it. |
account_sid | string | — | Exotel Account SID |
phone_number | string | — | Phone number |
Parameters from the server's own tool schema.
Why create_phone_number_route is rated Medium
An AI agent can call create_phone_number_route faster than any human can review: one bad instruction and it creates or modifies resources in Elevenlabs by the hundred, each call as confident as the last.
Risk signalsHandles credentials or secrets (token) · High parameter count (19 properties)
Attacks that exploit this kind of access
The rule that runs create_phone_number_route safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elevenlabs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_phone_number_route, this is the rule to start with:
create_phone_number_route 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Elevenlabs, apply this rule, and every create_phone_number_route call is checked against it from then on.
Questions about create_phone_number_route
Import Phone Number. It is categorised as a Write tool in the Elevenlabs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_phone_number_route accepts 12 parameters: sid, label, token, app_id, api_key, agent_id, provider, api_token, applet_url, enable_sms, account_sid, phone_number. The full parameter table on this page comes from the server's own tool schema.
Register the Elevenlabs MCP server in PolicyLayer and add a rule for create_phone_number_route: 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 Elevenlabs. Nothing to install.
create_phone_number_route 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 create_phone_number_route 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 create_phone_number_route. 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.
create_phone_number_route is provided by the Elevenlabs MCP server (@aiwerk/mcp-server-elevenlabs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elevenlabs, and thousands of servers like it.
This server
Across the catalogue