ghl_create_relation
Create a relation between two entities using an existing association. Links specific records together.
This record as markdown: /tools/ghl/ghl-create-relation.md
What ghl_create_relation does on Ghl
AI agents use ghl_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 | — | GoHighLevel location ID (will use default if not provided) |
associationId | string | Yes | The ID of the association to use for this relation |
firstRecordId | string | Yes | ID of the first record (e.g., contact ID if contact is first object in association) |
secondRecordId | string | Yes | ID of the second record (e.g., custom object record ID if custom object is second object) |
Parameters from the server's own tool schema.
Why ghl_create_relation is rated Medium
Creating relations between entities modifies data structure by establishing new links, which is reversible (relations can be deleted). This is a Write operation rather than Read (retrieves data with no side effects) or Execute (runs arbitrary code).
From the tool's definition Tool name contains 'create' and description states 'Create a relation between two entities' and 'Links specific records together.' This is a create/write operation that establishes new associations between existing records.
Attacks that exploit this kind of access
The rule that runs ghl_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 ghl_create_relation, this is the rule to start with:
ghl_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 ghl_create_relation call is checked against it from then on.
Questions about ghl_create_relation
Create a relation between two entities using an existing association. Links specific records together. 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.
ghl_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 ghl_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.
ghl_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 ghl_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 ghl_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.
ghl_create_relation 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