ghl_get_custom_field_by_id
Get a custom field or folder by its ID. Supports custom objects and company (business) fields.
This record as markdown: /tools/ghl/ghl-get-custom-field-by-id.md
What ghl_get_custom_field_by_id does on Ghl
AI agents call ghl_get_custom_field_by_id 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 |
|---|---|---|---|
id | string | Yes | The ID of the custom field or folder to retrieve |
Parameters from the server's own tool schema.
Why ghl_get_custom_field_by_id is rated Low
This tool queries and retrieves data about custom fields or folders by identifier. It performs no writes, deletions, code execution, or financial operations. The verb 'Get' and the absence of any mutation language confirm this is a Read operation. Severity is low because retrieving field metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description explicitly states 'Get a custom field or folder by its ID' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs ghl_get_custom_field_by_id 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_custom_field_by_id, this is the rule to start with:
ghl_get_custom_field_by_id 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_custom_field_by_id call is checked against it from then on.
Questions about ghl_get_custom_field_by_id
Get a custom field or folder by its ID. Supports custom objects and company (business) fields. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
ghl_get_custom_field_by_id accepts 1 parameter: id. Required: id. 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_custom_field_by_id: 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_custom_field_by_id 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_custom_field_by_id 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_custom_field_by_id. 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_custom_field_by_id 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