ghl_get_association_by_key
Get an association by its key name. Useful for finding both standard and user-defined associations.
This record as markdown: /tools/ghl/ghl-get-association-by-key.md
What ghl_get_association_by_key does on Ghl
AI agents call ghl_get_association_by_key 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 |
|---|---|---|---|
keyName | string | Yes | The key name of the association to retrieve |
locationId | string | — | GoHighLevel location ID (will use default if not provided) |
Parameters from the server's own tool schema.
Why ghl_get_association_by_key is rated Low
This tool retrieves association data by key lookup without side effects. The 'get' verb and read-only language ('finding', 'retrieve') indicate a pure data query operation. No creation, modification, deletion, or execution capability is described. Severity is low because reading association metadata poses minimal risk of harm even in adversarial use.
From the tool's definition Tool name includes 'get_' and description states 'Get an association by its key name...finding...associations' with no mention of modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs ghl_get_association_by_key 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_association_by_key, this is the rule to start with:
ghl_get_association_by_key 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_association_by_key call is checked against it from then on.
Questions about ghl_get_association_by_key
Get an association by its key name. Useful for finding both standard and user-defined associations. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
ghl_get_association_by_key accepts 2 parameters: keyName, locationId. Required: keyName. 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_association_by_key: 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_association_by_key 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_association_by_key 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_association_by_key. 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_association_by_key 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