Query your call history, results, and analytics. Use to: - Check the result of a specific call (by call_id) - View recent call history for an agent - Get aggregate analytics with conversion rates, top objections, and AI recommendations The analytics include AI-generated recommendations for improv...
AI agents call vora_calls to retrieve information from Vora without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query tool that retrieves historical call data and analytics. While it accesses potentially sensitive call recordings, transcripts, and business metrics (which justifies medium severity for data exposure risk), it performs no destructive, financial, or code execution actions. The tool does not create, modify, or delete data—it only retrieves and analyzes existing call records.
From the tool's definition Tool description explicitly states 'Query your call history, results, and analytics' with capabilities to 'Check the result of a specific call', 'View recent call history', and 'Get aggregate analytics'.
Attacks that exploit this kind of access
Query your call history, results, and analytics. Use to: - Check the result of a specific call (by call_id) - View recent call history for an agent - Get aggregate analytics with conversion rates, top objections, and AI recommendations The analytics include AI-generated recommendations for improving your calls. It is categorised as a Read tool in the Vora MCP Server, which means it retrieves data without modifying state.
Register the Vora MCP server in PolicyLayer and add a rule for vora_calls: 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_calls 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 vora_calls 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_calls. 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_calls 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 →