calls_get_transcript
Get the structured transcript and final state of a voice call by call_id. Returns per-turn rows in chronological order, call status (active/completed/failed/abandoned), duration, and an outcome field telling whether the recipient picked up (answered/no_answer/busy/declined/failed/unknown). answer...
This record as markdown: /tools/io-github-saloprj-dialogbrain/calls-get-transcript.md
What calls_get_transcript does on Dialogbrain
AI agents call calls_get_transcript to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
call_id | string | Yes | Call ID returned by calls.make in _meta.call_id. |
Parameters from the server's own tool schema.
Why calls_get_transcript is rated Low
This tool retrieves historical call transcripts and metadata (status, duration, outcome). It performs a read-only query operation with no ability to modify, delete, or trigger actions on the underlying call data. The blast radius of misuse is limited to potential exposure of call content/metadata, classified as low severity for a read operation.
From the tool's definition Tool description states it 'Get[s] the structured transcript and final state of a voice call' and 'Returns per-turn rows' — operations that retrieve and query existing call data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs calls_get_transcript safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For calls_get_transcript, this is the rule to start with:
calls_get_transcript is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every calls_get_transcript call is checked against it from then on.
Questions about calls_get_transcript
Get the structured transcript and final state of a voice call by call_id. Returns per-turn rows in chronological order, call status (active/completed/failed/abandoned), duration, and an outcome field telling whether the recipient picked up (answered/no_answer/busy/declined/failed/unknown). answered_at is non-null once the recipient picked up. Returns active turns if the call is still in progress. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
calls_get_transcript accepts 1 parameter: call_id. Required: call_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for calls_get_transcript: 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 Dialogbrain. Nothing to install.
calls_get_transcript 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 calls_get_transcript 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 calls_get_transcript. 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.
calls_get_transcript is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue