whatsapp_outbound_call
Make An Outbound Call Via Whatsapp.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/whatsapp-outbound-call.md
What whatsapp_outbound_call does on Elevenlabs
AI agents call whatsapp_outbound_call to retrieve information from Elevenlabs without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | Yes | |
whatsapp_user_id | string | Yes | |
whatsapp_phone_number_id | string | Yes | |
conversation_initiation_client_data | object | — | |
whatsapp_call_permission_request_template_name | string | Yes | |
whatsapp_call_permission_request_template_language_code | string | Yes |
Parameters from the server's own tool schema.
Why whatsapp_outbound_call is rated Low
Even though whatsapp_outbound_call only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs whatsapp_outbound_call 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 whatsapp_outbound_call, this is the rule to start with:
whatsapp_outbound_call is read-only, so it stays allowed. 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 whatsapp_outbound_call call is checked against it from then on.
Questions about whatsapp_outbound_call
Make An Outbound Call Via Whatsapp. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
whatsapp_outbound_call accepts 6 parameters: agent_id, whatsapp_user_id, whatsapp_phone_number_id, conversation_initiation_client_data, whatsapp_call_permission_request_template_name, whatsapp_call_permission_request_template_language_code. Required: agent_id, whatsapp_user_id, whatsapp_phone_number_id, whatsapp_call_permission_request_template_name, whatsapp_call_permission_request_template_language_code. 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 whatsapp_outbound_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 Elevenlabs. Nothing to install.
whatsapp_outbound_call is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the whatsapp_outbound_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 whatsapp_outbound_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.
whatsapp_outbound_call 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