ghl_get_relations_by_record

Get all relations for a specific record ID with pagination and optional filtering by association IDs.

Server GoHighLevel MCP Server keshigami/ghl-mcp-workiong
Category Read
Risk class Low
Parameters 00 required

What ghl_get_relations_by_record does on GoHighLevel MCP Server

AI agents call ghl_get_relations_by_record to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why ghl_get_relations_by_record needs a policy

This tool retrieves relationship/association data for a record. It is a read-only query operation that returns existing data about record relations. There is no creation, modification, deletion, or execution of operations. The pagination and filtering parameters are typical for read operations.

From the tool's definition Tool description: 'Get all relations for a specific record ID with pagination and optional filtering by association IDs.' The verb 'Get' and operation 'retrieve relations' indicate data retrieval without modification. No side effects, no state changes.

Questions about ghl_get_relations_by_record

What does the ghl_get_relations_by_record tool do? +

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 GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ghl_get_relations_by_record? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.

What risk level is ghl_get_relations_by_record? +

ghl_get_relations_by_record is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ghl_get_relations_by_record? +

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.

How do I block ghl_get_relations_by_record completely? +

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.

What MCP server provides ghl_get_relations_by_record? +

ghl_get_relations_by_record is provided by the GoHighLevel MCP Server MCP server (keshigami/ghl-mcp-workiong). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.