contacts_profile
👤 Get full profile for a contact: all channel identities, notes, role, capabilities, birthday. When to use: - After contacts.find to get complete info about a specific person - To see all channels a contact is reachable on - To read notes, role, or capabilities for a contact Requires contact_id ...
This record as markdown: /tools/io-github-saloprj-dialogbrain/contacts-profile.md
What contacts_profile does on Dialogbrain
AI agents call contacts_profile 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 |
|---|---|---|---|
contact_id | string | Yes | entity_id from contacts.find |
Parameters from the server's own tool schema.
Why contacts_profile is rated Low
This tool queries and returns existing contact data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves contact profile details. Low severity because exposure only allows viewing contact information without enabling message sending, financial actions, or destructive operations.
From the tool's definition Tool retrieves contact profile information including 'all channel identities, notes, role, capabilities, birthday' with no side effects. Description explicitly states 'Get' and 'read notes' indicating data retrieval only.
Attacks that exploit this kind of access
The rule that runs contacts_profile 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_profile, this is the rule to start with:
contacts_profile 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_profile call is checked against it from then on.
Questions about contacts_profile
👤 Get full profile for a contact: all channel identities, notes, role, capabilities, birthday. When to use: - After contacts.find to get complete info about a specific person - To see all channels a contact is reachable on - To read notes, role, or capabilities for a contact Requires contact_id (entity_id) from contacts.find. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
contacts_profile accepts 1 parameter: contact_id. 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_profile: 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_profile 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_profile 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_profile. 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_profile 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