Call a candidate to inform them about their interview results
AI agents invoke notify_interview_result to trigger actions in Voice Assistant 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.
This tool initiates a real-world phone call to a candidate, which is an external operation with tangible effects (contacting a real person with potentially life-affecting information about their job application). It goes beyond mere data writing since it executes a live voice communication.
From the tool's definition 'Call a candidate to inform them about their interview results' — triggers an outbound phone call via Twilio to an external party
Attacks that exploit this kind of access
Call a candidate to inform them about their interview results. It is categorised as a Execute tool in the Voice Assistant MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Voice Assistant MCP Server MCP server in PolicyLayer and add a rule for notify_interview_result: 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 Voice Assistant MCP Server. Nothing to install.
notify_interview_result 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 notify_interview_result 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 notify_interview_result. 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.
notify_interview_result is provided by the Voice Assistant MCP Server MCP server (prakharbhardwaj/voice-agent-mcp-server). 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 →