This record as markdown: /tools/aiwerk-mcp-server-ghl/contacts-create-association.md
What contacts_create_association does on Ghl
AI agents use contacts_create_association 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 | Yes | list of tags to be added or removed |
type | string | Yes | Path parameter type. |
contacts | array | Yes | list of contact ids to be processed |
locationId | string | — | location id from where the bulk request is executed Defaults to GHL_LOCATION_ID when omitted. |
removeAllTags | boolean | — | Option to implement remove all tags. if true, all tags will be removed from the contacts. Can only be used with remove type. |
Parameters from the server's own tool schema.
Why contacts_create_association is rated Medium
An AI agent can call contacts_create_association faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs contacts_create_association 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 contacts_create_association, this is the rule to start with:
contacts_create_association 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 contacts_create_association call is checked against it from then on.
Questions about contacts_create_association
Update Contacts Tags. 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.
contacts_create_association accepts 5 parameters: tags, type, contacts, locationId, removeAllTags. Required: tags, type, contacts. 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 contacts_create_association: 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.
contacts_create_association 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_create_association 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_create_association. 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_create_association is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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