Check status of a previously initiated voice call or get status of all active calls.
AI agents call check_call_status to retrieve information from Telephony MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves information about existing calls without modifying, executing, or affecting any telephony operations. It is a passive status check similar to fetching metadata. While telephony systems can be sensitive, merely querying call status poses minimal risk compared to the sibling tools (send_sms, voice_call, voice_call_with_input) which actively initiate communications.
From the tool's definition Tool description states 'Check status of a previously initiated voice call' and 'get status of all active calls' — these are pure query/lookup operations with no side effects.
Attacks that exploit this kind of access
Check status of a previously initiated voice call or get status of all active calls. It is categorised as a Read tool in the Telephony MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Telephony MCP Server MCP server in PolicyLayer and add a rule for check_call_status: 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 Telephony MCP Server. Nothing to install.
check_call_status 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 check_call_status 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 check_call_status. 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.
check_call_status is provided by the Telephony MCP Server MCP server (vonage-community/telephony-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 →