This record as markdown: /tools/ghl/update-contact.md
What update_contact does on Ghl
AI agents use update_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 |
lastName | string | — | Contact last name |
contactId | string | Yes | Contact ID |
firstName | string | — | Contact first name |
Parameters from the server's own tool schema.
Why update_contact is rated Medium
This tool modifies contact records reversibly—a core Write operation. The medium severity reflects that incorrect updates could disrupt CRM data and customer relationships, but changes are not irreversible and the blast radius is limited to contact metadata rather than financial or destructive operations.
From the tool's definition Tool name 'update_contact' and description 'Update contact information' indicate modification of existing contact data without deletion or destruction.
Attacks that exploit this kind of access
The rule that runs update_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 update_contact, this is the rule to start with:
update_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 update_contact call is checked against it from then on.
Questions about update_contact
Update contact information. 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.
update_contact accepts 6 parameters: tags, email, phone, lastName, contactId, firstName. Required: contactId. 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 update_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.
update_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 update_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 update_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.
update_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