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 call status information—a read-only operation with no side effects. While the Telephony MCP Server as a whole contains tools capable of making calls and sending messages (Execute/Write category), check_call_status itself is purely informational.
From the tool's definition The tool description explicitly states it "Check[s] status of a previously initiated voice call" and retrieves "status of all active calls." These are query operations that retrieve information about existing calls without modifying, executing, or deleting…
Documented attack patterns abuse exactly the kind of access check_call_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telephony MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_call_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_call_status": {}
}
}check_call_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 (khan2a/telephony-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telephony MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Telephony MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.