ghl_get_relations_by_record
Get all relations for a specific record ID with pagination and optional filtering by association IDs.
This record as markdown: /tools/ghl/ghl-get-relations-by-record.md
What ghl_get_relations_by_record does on Ghl
AI agents call ghl_get_relations_by_record to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
skip | number | — | Number of records to skip for pagination |
limit | number | — | Maximum number of records to return |
recordId | string | Yes | The record ID to get relations for |
locationId | string | — | GoHighLevel location ID (will use default if not provided) |
associationIds | array | — | Optional array of association IDs to filter relations |
Parameters from the server's own tool schema.
Why ghl_get_relations_by_record is rated Low
This tool retrieves data about relationships/relations associated with a record. It performs a GET-like operation that queries existing data without creating, modifying, or deleting anything. The inclusion of pagination and filtering parameters further confirms it is a read operation. No side effects or data mutations are indicated.
From the tool's definition The tool name contains 'get' and the description states it retrieves 'all relations for a specific record ID' with 'pagination and optional filtering'. These are characteristic read-only query operations with no side effects.
Attacks that exploit this kind of access
The rule that runs ghl_get_relations_by_record 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_get_relations_by_record, this is the rule to start with:
ghl_get_relations_by_record is read-only, so it stays allowed. 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_get_relations_by_record call is checked against it from then on.
Questions about ghl_get_relations_by_record
Get all relations for a specific record ID with pagination and optional filtering by association IDs. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
ghl_get_relations_by_record accepts 5 parameters: skip, limit, recordId, locationId, associationIds. Required: recordId. 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_get_relations_by_record: 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_get_relations_by_record is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ghl_get_relations_by_record 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_get_relations_by_record. 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_get_relations_by_record 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