associations_create_relation
Create Relation for you associated entities.
This record as markdown: /tools/aiwerk-mcp-server-ghl/associations-create-relation.md
What associations_create_relation does on Ghl
AI agents use associations_create_relation 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 |
|---|---|---|---|
locationId | string | — | Your Sub Account's ID Defaults to GHL_LOCATION_ID when omitted. |
associationId | string | Yes | Association's Id |
firstRecordId | string | Yes | First Record's Id. For instance, if you have an association between a contact and a custom object, and you specify the contact as the first object while creatin |
secondRecordId | string | Yes | Second Record's Id.For instance, if you have an association between a contact and a custom object, and you specify the custom object as the second entity while |
Parameters from the server's own tool schema.
Why associations_create_relation is rated Medium
An AI agent can call associations_create_relation 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 associations_create_relation 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 associations_create_relation, this is the rule to start with:
associations_create_relation 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 associations_create_relation call is checked against it from then on.
Questions about associations_create_relation
Create Relation for you associated entities. 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.
associations_create_relation accepts 4 parameters: locationId, associationId, firstRecordId, secondRecordId. Required: associationId, firstRecordId, secondRecordId. 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 associations_create_relation: 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.
associations_create_relation 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 associations_create_relation 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 associations_create_relation. 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.
associations_create_relation 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