contacts_capture_lead
📝 Save a website-chat visitor's details as a structured lead (contact + Contacts tab). When to use: - In a livechat conversation, AFTER the visitor has shared their name and email (plus company / use case if given) — e.g. when booking a demo. - Call it once you have the details; then continue (e...
This record as markdown: /tools/io-github-saloprj-dialogbrain/contacts-capture-lead.md
What contacts_capture_lead does on Dialogbrain
AI agents use contacts_capture_lead 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 |
|---|---|---|---|
name | string | Yes | The visitor's full name (as they gave it). |
email | string | — | The visitor's email address. |
phone | string | — | Phone number, if the visitor provided one. |
company | string | — | The visitor's company / organization, if mentioned. |
use_case | string | — | Their main use case / what they want to do with DialogBrain, if mentioned. |
Parameters from the server's own tool schema.
Why contacts_capture_lead is rated Medium
This tool creates and modifies data (contact records and lead entries) in a reversible manner. While it stores personal information (name, email, company), the action is not destructive—records can be edited or deleted later. It is Write rather than Read because it actively persists new data structures.
From the tool's definition Tool performs 'Save' operation, 'Creates/links a contact record and a lead entry', modifying data in the Contacts system by adding new records.
Attacks that exploit this kind of access
The rule that runs contacts_capture_lead 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_capture_lead, this is the rule to start with:
contacts_capture_lead 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_capture_lead call is checked against it from then on.
Questions about contacts_capture_lead
📝 Save a website-chat visitor's details as a structured lead (contact + Contacts tab). When to use: - In a livechat conversation, AFTER the visitor has shared their name and email (plus company / use case if given) — e.g. when booking a demo. - Call it once you have the details; then continue (e.g. share the booking link). Creates/links a contact record and a lead entry. Only works inside a website-chat thread. 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_capture_lead accepts 5 parameters: name, email, phone, company, use_case. Required: name. 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_capture_lead: 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_capture_lead 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_capture_lead 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_capture_lead. 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_capture_lead 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