contacts_research
Research a person before outreach: returns a synthesized profile (current role, company, location, career history, education, LinkedIn/social URLs) plus a candidates array for disambiguating namesakes. Use to personalize a first touch or brief before a meeting. Does NOT return contact channels (e...
This record as markdown: /tools/io-github-saloprj-dialogbrain/contacts-research.md
What contacts_research does on Dialogbrain
AI agents call contacts_research 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 | Who to research: full name plus any disambiguating context you have (company, role, location), e.g. '[full name], founder of [company]'. |
Parameters from the server's own tool schema.
Why contacts_research is rated Low
The tool only retrieves and synthesizes publicly available profile information about a person. It has no side effects, does not write or modify data, and explicitly states it does not return sensitive contact channels. It is a read-only lookup/research tool with low blast radius.
From the tool's definition Research a person before outreach: returns a synthesized profile (current role, company, location, career history, education, LinkedIn/social URLs)... Does NOT return contact channels (email/phone/telegram)
Attacks that exploit this kind of access
The rule that runs contacts_research 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_research, this is the rule to start with:
contacts_research 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_research call is checked against it from then on.
Questions about contacts_research
Research a person before outreach: returns a synthesized profile (current role, company, location, career history, education, LinkedIn/social URLs) plus a candidates array for disambiguating namesakes. Use to personalize a first touch or brief before a meeting. Does NOT return contact channels (email/phone/telegram) — use contacts.discover to add a reachable channel, or the LinkedIn URL from the result for a connection request. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
contacts_research accepts 1 parameter: query. Required: query. 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_research: 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_research 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_research 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_research. 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_research 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