search_threads
Find or list chat threads/conversations — by topic, participant, unread/unanswered status, or recency. Omit query to list threads by filter. For message content use search.messages; for files use search.files. since filters by recency and pairs with only_unread / only_unanswered.
This record as markdown: /tools/io-github-saloprj-dialogbrain/search-threads.md
What search_threads does on Dialogbrain
AI agents call search_threads 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 threads to return. |
query | string | — | Topic/keyword to search threads for. OMIT to list threads by filter. |
since | string | — | ISO date (YYYY-MM-DD). Only threads with any message activity since this date (recency filter, not 'unanswered'). OMIT to skip. |
only_unread | boolean | — | Limit to threads with unread messages. OMIT to include read threads. |
only_unanswered | boolean | — | Limit to threads where the last message is incoming (you haven't replied). Covers 'threads I haven't replied to'. OMIT to include answered threads too. |
participant_name | string | — | Filter to threads with this participant/contact. OMIT to include everyone (do NOT pass an empty string). |
include_last_messages | integer | — | With only_unanswered: inline the most recent N messages (0-2) per thread so one call is enough to draft replies. Text truncated to 150 chars; full body via mess |
Parameters from the server's own tool schema.
Why search_threads is rated Low
search_threads retrieves and queries conversation metadata (threads, participants, status flags like unread/unanswered, recency). It has no side effects—it does not create, modify, delete, or execute any external operations. The severity is low because misuse is limited to information disclosure with no capability to alter or harm systems beyond unauthorized data access.
From the tool's definition Tool description states 'Find or list chat threads/conversations' and 'Omit query to list threads by filter.' The tool performs search and filtering operations without modifying data.
Attacks that exploit this kind of access
The rule that runs search_threads 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 search_threads, this is the rule to start with:
search_threads 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 search_threads call is checked against it from then on.
Questions about search_threads
Find or list chat threads/conversations — by topic, participant, unread/unanswered status, or recency. Omit query to list threads by filter. For message content use search.messages; for files use search.files. since filters by recency and pairs with only_unread / only_unanswered. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
search_threads accepts 7 parameters: limit, query, since, only_unread, only_unanswered, participant_name, include_last_messages. 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 search_threads: 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.
search_threads 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 search_threads 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 search_threads. 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.
search_threads 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