messages_read_history
Read messages from a conversation thread. Use text_contains to find specific messages by content. Returns the most recent messages, including sender info and timestamps. Voice calls: each row carries a meta object with allowlisted keys (event_type ∈ 'call_started'|'call_ended'|null, source ∈ 'voi...
This record as markdown: /tools/io-github-saloprj-dialogbrain/messages-read-history.md
What messages_read_history does on Dialogbrain
AI agents call messages_read_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 number of messages to return (default: 10, max: 100) |
offset | integer | — | Number of messages to skip (for pagination, default: 0) |
thread_id | string | — | Thread ID to read messages from (e.g., '571' or 'telegram:571'). Optional if contact_name provided. |
contact_name | string | — | Contact/thread name to search for (optional if thread_id provided). Example: 'Jane Smith', 'John Doe' |
text_contains | string | — | Filter: only return messages containing this text (case-insensitive substring match) |
include_outgoing | boolean | — | Include messages sent by you (default: true) |
Parameters from the server's own tool schema.
Why messages_read_history is rated Low
This tool retrieves historical message data from conversations without side effects. It queries existing data across WhatsApp, Telegram, Email, and voice channels, making it a Read operation. The low severity reflects minimal blast radius—an AI agent misusing this tool could access message history it shouldn't, but cannot modify, delete, or trigger external actions.
From the tool's definition Tool description states 'Read messages from a conversation thread' and 'Returns the most recent messages'. The primary action is retrieval with the `text_contains` parameter for filtering—no creation, modification, or deletion of data occurs.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs messages_read_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 messages_read_history, this is the rule to start with:
messages_read_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 messages_read_history call is checked against it from then on.
Questions about messages_read_history
Read messages from a conversation thread. Use text_contains to find specific messages by content. Returns the most recent messages, including sender info and timestamps. Voice calls: each row carries a meta object with allowlisted keys (event_type ∈ 'call_started'|'call_ended'|null, source ∈ 'voice_transcript'|null, call_id, speaker_display_name, duration_seconds, outcome, direction) plus per-message channel. To find calls without scanning every row, use calls.list_history instead. Usage: 1. Get thread_id from threads.list first, OR 2. Use contact_name to auto-resolve thread_id Examples: - User: 'show me messages from chat with [contact]' → read_history(contact_name='[contact]', limit=10) - User: 'last 5 messages from thread 571' → read_history(thread_id=571, limit=5). It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
messages_read_history accepts 6 parameters: limit, offset, thread_id, contact_name, text_contains, include_outgoing. 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 messages_read_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.
messages_read_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 messages_read_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 messages_read_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.
messages_read_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