make_outbound_call
AI agents invoke make_outbound_call to trigger actions in ElevenLabs MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name strongly implies initiating an outbound phone call, which is an external operation with real-world effects (contacting people, using phone minutes/credits). This falls under Execute as it triggers an external operation. The blast radius is high because an AI agent could use this to call arbitrary numbers, potentially harassing individuals or incurring costs.
From the tool's definition Tool name 'make_outbound_call' on a server with phone number capabilities ('list_phone_numbers' sibling tool) and voice/audio generation features. Description is empty.
Attacks that exploit this kind of access
make_outbound_call. It is categorised as a Execute tool in the ElevenLabs MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ElevenLabs MCP Server MCP server in PolicyLayer and add a rule for make_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 MCP Server. Nothing to install.
make_outbound_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the make_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 make_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.
make_outbound_call is provided by the ElevenLabs MCP Server MCP server (nguyendinhsinh361/elevenlabs-mcp). 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 →