Report whether a call is currently active (debug/sanity).
AI agents call call_status to retrieve information from Ringback without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and reports the status of an active call—no side effects, no modifications, no external operations triggered. It is a pure information-retrieval function similar to checking a flag or querying a state variable. The blast radius if misused is minimal: an agent could learn call status but cannot initiate, end, modify, or interact with calls via this tool alone.
From the tool's definition Tool name 'call_status' and description 'Report whether a call is currently active' indicate a query operation that retrieves state information without modifying or triggering any external actions.
Documented attack patterns abuse exactly the kind of access call_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ringback, and nothing reaches the server without passing your rules. This is the rule we recommend for call_status:
{
"version": "1",
"default": "deny",
"tools": {
"call_status": {}
}
}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.
Report whether a call is currently active (debug/sanity). It is categorised as a Read tool in the Ringback MCP Server, which means it retrieves data without modifying state.
Register the Ringback MCP server in PolicyLayer and add a rule for 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 Ringback. Nothing to install.
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 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 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.
call_status is provided by the Ringback MCP server (mohitbadwal/ringback). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ringback, 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.
12 Ringback tools catalogued and risk-classified — across an index of 43,000+ MCP servers.