contacts_sync
Add a discovered contact and open a conversation thread. Returns thread_id for the new conversation, plus entity_id — the canonical handle to pass as contacts.update's contact_id. Call contacts.discover first to verify the contact exists.
This record as markdown: /tools/io-github-saloprj-dialogbrain/contacts-sync.md
What contacts_sync does on Dialogbrain
AI agents use contacts_sync to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
channel | string | Yes | Channel name: telegram, whatsapp, etc. |
identifier | string | Yes | Username or phone number to add |
Parameters from the server's own tool schema.
Why contacts_sync is rated Medium
This tool creates new contacts and conversation threads in a messaging system. While the operations are reversible (contacts can be deleted, threads closed), they modify persistent state. The tool does not retrieve data only (Read), does not execute arbitrary code (Execute), does not permanently delete (Destructive), and involves no financial transactions (Financial).
From the tool's definition "Add a discovered contact and open a conversation thread. Returns thread_id for the new conversation, plus entity_id" - creates new contact and conversation, both reversible modifications.
Attacks that exploit this kind of access
The rule that runs contacts_sync 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_sync, this is the rule to start with:
contacts_sync stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_sync call is checked against it from then on.
Questions about contacts_sync
Add a discovered contact and open a conversation thread. Returns thread_id for the new conversation, plus entity_id — the canonical handle to pass as contacts.update's contact_id. Call contacts.discover first to verify the contact exists. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
contacts_sync accepts 2 parameters: channel, identifier. Required: channel, identifier. 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_sync: 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_sync is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the contacts_sync 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_sync. 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_sync 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