contacts_discover
Search for a contact on a live channel (Telegram, WhatsApp, etc.) before adding them. Use this to look up a person by username or phone number before calling contacts.sync. This is the right tool when asked to add or find a specific person by @username or phone (use contacts.sync afterwards to ac...
This record as markdown: /tools/io-github-saloprj-dialogbrain/contacts-discover.md
What contacts_discover does on Dialogbrain
AI agents call contacts_discover 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 |
|---|---|---|---|
query | string | Yes | Username, phone, or name to search for |
channel | string | Yes | Channel name: telegram, whatsapp, etc. |
Parameters from the server's own tool schema.
Why contacts_discover is rated Low
The tool only searches/queries for contact information on external channels. It does not add, modify, or delete any data; the description explicitly notes that contacts.sync must be called separately to actually add the contact. This is a read-only discovery operation.
From the tool's definition 'Search for a contact on a live channel... look up a person by username or phone number before calling contacts.sync' — purely a lookup/search operation with no side effects
Attacks that exploit this kind of access
The rule that runs contacts_discover 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 contacts_discover, this is the rule to start with:
contacts_discover 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 contacts_discover call is checked against it from then on.
Questions about contacts_discover
Search for a contact on a live channel (Telegram, WhatsApp, etc.) before adding them. Use this to look up a person by username or phone number before calling contacts.sync. This is the right tool when asked to add or find a specific person by @username or phone (use contacts.sync afterwards to actually add them) — not group_discovery. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
contacts_discover accepts 2 parameters: query, channel. Required: query, channel. 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 contacts_discover: 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.
contacts_discover 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 contacts_discover 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 contacts_discover. 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.
contacts_discover 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