Return the full call transcript so far — both sides, with interruptions.
AI agents call get_conversation 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 retrieves and queries an existing call transcript. It performs no modifications, deletions, or external operations—purely a read operation that returns stored conversation data. The blast radius if misused (e.g., an agent leaking transcript content) is limited to information disclosure rather than system compromise or irreversible damage.
From the tool's definition Tool name 'get_conversation' and description 'Return the full call transcript so far — both sides, with interruptions' indicates data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get_conversation 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 get_conversation:
{
"version": "1",
"default": "deny",
"tools": {
"get_conversation": {}
}
}get_conversation 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.
Return the full call transcript so far — both sides, with interruptions. 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 get_conversation: 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.
get_conversation 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 get_conversation 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 get_conversation. 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.
get_conversation 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.