contacts_update
✏️ Update a contact's profile: name, notes, role, capabilities, birthday, preferred channel. When to use: - User wants to add notes about a contact - User wants to set/update role or capabilities for a contact - User wants to rename a contact or update birthday Requires contact_id — the entity_id...
This record as markdown: /tools/io-github-saloprj-dialogbrain/contacts-update.md
What contacts_update does on Dialogbrain
AI agents use contacts_update 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 |
|---|---|---|---|
role | string | — | Contact role (e.g. developer, client, partner). Empty string clears role. |
notes | string | — | Free-text notes/context about this contact. Empty string clears notes. |
contact_id | string | Yes | entity_id from contacts.find or contacts.sync |
birthday_day | integer | — | Birth day 1-31 (must be set together with birthday_month) |
capabilities | array | — | List of capabilities (e.g. ['backend', 'design']) |
display_name | string | — | New display name (max 255 chars) |
birthday_year | integer | — | Birth year 1900-2100 (optional, standalone) |
birthday_month | integer | — | Birth month 1-12 (must be set together with birthday_day) |
preferred_channel | string | — | Preferred channel for contacting this person. OMIT to leave the preferred channel unchanged. |
Parameters from the server's own tool schema.
Why contacts_update is rated Medium
This tool creates or modifies contact data reversibly. It updates existing contact records with new information but does not delete data or execute external operations. The changes are reversible—profiles can be updated again or reverted.
From the tool's definition Tool description states 'Update a contact's profile' with fields like 'name, notes, role, capabilities, birthday, preferred channel.' The context 'When to use' confirms modification operations: 'add notes', 'set/update role', 'rename a contact', 'update…
Attacks that exploit this kind of access
The rule that runs contacts_update 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_update, this is the rule to start with:
contacts_update 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_update call is checked against it from then on.
Questions about contacts_update
✏️ Update a contact's profile: name, notes, role, capabilities, birthday, preferred channel. When to use: - User wants to add notes about a contact - User wants to set/update role or capabilities for a contact - User wants to rename a contact or update birthday Requires contact_id — the entity_id returned by contacts.find or contacts.sync. At least one optional field must be provided. 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_update accepts 9 parameters: role, notes, contact_id, birthday_day, capabilities, display_name, birthday_year, birthday_month, preferred_channel. Required: contact_id. 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_update: 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_update 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_update 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_update. 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_update 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