upsert_contact
Create or update contact based on email/phone (smart merge)
This record as markdown: /tools/ghl/upsert-contact.md
What upsert_contact does on Ghl
AI agents use upsert_contact to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | array | — | Tags to assign to contact |
email | string | — | Contact email address |
phone | string | — | Contact phone number |
source | string | — | Source of the contact |
lastName | string | — | Contact last name |
firstName | string | — | Contact first name |
assignedTo | string | — | User ID to assign contact to |
Parameters from the server's own tool schema.
Why upsert_contact is rated Medium
This tool creates new contacts or updates existing ones based on matching criteria (email/phone). While the operations are reversible (contacts can be modified again or deleted separately), the ability to merge and modify contact data across a CRM system represents a significant write capability with potential impact on business data integrity.
From the tool's definition Tool description states 'Create or update contact' which are write operations. The 'smart merge' functionality indicates it modifies existing contact records based on email/phone matching, making this a reversible data modification tool rather than…
Attacks that exploit this kind of access
The rule that runs upsert_contact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upsert_contact, this is the rule to start with:
upsert_contact 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 Ghl, apply this rule, and every upsert_contact call is checked against it from then on.
Questions about upsert_contact
Create or update contact based on email/phone (smart merge). It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
upsert_contact accepts 7 parameters: tags, email, phone, source, lastName, firstName, assignedTo. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for upsert_contact: 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 Ghl. Nothing to install.
upsert_contact 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 upsert_contact 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 upsert_contact. 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.
upsert_contact is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue