This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/create-batch-call.md
What create_batch_call does on Elevenlabs
AI agents use create_batch_call 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 |
|---|---|---|---|
agent_id | string | Yes | |
timezone | string | null | — | |
branch_id | string | null | — | |
call_name | string | Yes | |
recipients | array | Yes | |
environment | string | null | — | |
whatsapp_params | object | — | |
scheduled_time_unix | number | null | — | |
agent_phone_number_id | string | null | — | |
telephony_call_config | object | — | |
target_concurrency_limit | number | null | — |
Parameters from the server's own tool schema.
Why create_batch_call is rated Medium
An AI agent can call create_batch_call 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 signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
The rule that runs create_batch_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 create_batch_call, this is the rule to start with:
create_batch_call 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_batch_call call is checked against it from then on.
Questions about create_batch_call
Submit A Batch Call Request. 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_batch_call accepts 11 parameters: agent_id, timezone, branch_id, call_name, recipients, environment, whatsapp_params, scheduled_time_unix, agent_phone_number_id, telephony_call_config, target_concurrency_limit. Required: agent_id, call_name, recipients. 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_batch_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.
create_batch_call 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_batch_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 create_batch_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.
create_batch_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