calls_list_history
Search historical voice calls in this workspace by participant name, contact_id, thread, channel, source, and/or date range. Returns one row per call (NOT per turn) with call_id, duration_seconds, outcome, direction, started_at, source, channel_label, and parent_thread_id (the originating chat th...
This record as markdown: /tools/io-github-saloprj-dialogbrain/calls-list-history.md
What calls_list_history does on Dialogbrain
AI agents call calls_list_history 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 |
|---|---|---|---|
limit | integer | — | Maximum calls to return (default 20, max 100). |
since | string | — | ISO date or datetime lower bound (inclusive). Default: 90 days ago. Naive timestamps are interpreted as UTC. |
until | string | — | ISO date or datetime upper bound (inclusive). Default: now. |
source | string | — | Filter by voice_sessions.source: 'telegram' (1:1 + group), 'whatsapp' (native WhatsApp voice), 'twilio' (PSTN), 'meet' (Google Meet bot), 'livechat' (in-app voi |
channel | string | — | Filter by message-level channel of the call thread: 'telegram' (1:1 voice or group call sub-thread), 'twilio_voice', 'meet_voice', 'livechat_voice', 'whatsapp' |
thread_id | integer | — | Restrict to calls on this thread OR with this thread as their originating parent (Telegram group → call sub-thread back-link, Twilio outbound source_thread_id b |
contact_id | string | — | Filter by exact entity_id (from contacts.find). Mutually exclusive with participant_name when both target the same person. |
participant_name | string | — | Filter to calls whose parent thread has a participant matching this name (substring match against entity.title). Resolves group calls via the parent group's ros |
Parameters from the server's own tool schema.
Why calls_list_history is rated Low
This tool retrieves and queries existing call history metadata without creating, modifying, or deleting any data. It is a standard read operation analogous to list or search. The capability to search by various filters (participant name, date range, etc.) does not elevate it beyond Read category.
From the tool's definition Tool description states it "Search[es] historical voice calls" and "Returns one row per call" with metadata fields. The verb is search/query with no modification capability.
Attacks that exploit this kind of access
The rule that runs calls_list_history 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_list_history, this is the rule to start with:
calls_list_history 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_list_history call is checked against it from then on.
Questions about calls_list_history
Search historical voice calls in this workspace by participant name, contact_id, thread, channel, source, and/or date range. Returns one row per call (NOT per turn) with call_id, duration_seconds, outcome, direction, started_at, source, channel_label, and parent_thread_id (the originating chat thread for Telegram-group / Twilio-outbound / Meet calls). Pair with calls.get_transcript(call_id) for the full per-turn transcript. Use this instead of messages.read_history for cross-thread call queries — group calls and Meet sessions live on per-call sub-threads, not on the parent chat thread. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
calls_list_history accepts 8 parameters: limit, since, until, source, channel, thread_id, contact_id, participant_name. 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_list_history: 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_list_history 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_list_history 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_list_history. 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_list_history 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