Make an outbound phone call using your voice agent. Your agent handles the entire conversation autonomously — greeting, pitch, objection handling, qualification, closing — and returns a structured outcome. Calls typically take 1-5 minutes. You can poll vora_calls for the result or provide a callb...
AI agents invoke vora_call to trigger actions in Vora. 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.
This tool triggers an external real-world operation (an outbound phone call) with autonomous conversational actions. It is not merely writing data — it initiates live contact with a human being, conducts sales/qualification conversations, and produces outcomes. This qualifies as Execute due to triggering external operations whose effects depend on arguments.
From the tool's definition Make an outbound phone call using your voice agent. Your agent handles the entire conversation autonomously — greeting, pitch, objection handling, qualification, closing — and returns a structured outcome.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Make an outbound phone call using your voice agent. Your agent handles the entire conversation autonomously — greeting, pitch, objection handling, qualification, closing — and returns a structured outcome. Calls typically take 1-5 minutes. You can poll vora_calls for the result or provide a callback_url for async delivery. The more lead_context you provide, the better the conversation. Tell Vora everything you know about who it. It is categorised as a Execute tool in the Vora MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vora MCP server in PolicyLayer and add a rule for vora_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 Vora. Nothing to install.
vora_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 vora_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 vora_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.
vora_call is provided by the Vora MCP server (stefanstojanovicstefa-creator/vora-voice-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 →