# ghl_get_custom_field_by_id Get a custom field or folder by its ID. Supports custom objects and company (business) fields. Agent View of the PolicyLayer registry record for `ghl_get_custom_field_by_id`. HTML page: https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/ghl-get-custom-field-by-id ## Facts - Tool: `ghl_get_custom_field_by_id` - Server: GoHighLevel MCP Server (`thinkbedo/gohighlevel_mcp`) — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp.md - Homepage: https://github.com/ThinkBeDo/gohighlevel_mcp - Risk category: Read (Low risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Allowed ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "ghl_get_custom_field_by_id", "arguments": {} } } ``` ## Why ghl_get_custom_field_by_id is rated Low This tool retrieves field definitions and metadata by ID, with no indication of side effects, modification, deletion, or execution capabilities. It is analogous to fetching configuration or schema information, which is a read-only operation. The context of a CRM system containing sensitive data suggests data could be returned, but the tool itself only retrieves what already exists without altering it. From the tool's own definition: "'Get a custom field or folder by its ID' describes retrieval of field metadata without modification. The description indicates a query operation that fetches configuration/schema data about custom fields or folders." ## Use case AI agents call ghl_get_custom_field_by_id to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere. ## Recommended policy (PolicyLayer) Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches GoHighLevel MCP Server: ```json { "version": "1", "default": "deny", "tools": { "ghl_get_custom_field_by_id": {} } } ``` ## Other tools on GoHighLevel MCP Server (254) - `bulk_delete_social_posts` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/bulk-delete-social-posts.md - `cancel_scheduled_email` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/cancel-scheduled-email.md - `cancel_scheduled_message` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/cancel-scheduled-message.md - `delete_appointment` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-appointment.md - `delete_appointment_note` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-appointment-note.md - `delete_calendar` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-calendar.md - `delete_calendar_group` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-calendar-group.md - `delete_calendar_notification` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-calendar-notification.md - `delete_calendar_resource_equipment` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-calendar-resource-equipment.md - `delete_calendar_resource_room` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-calendar-resource-room.md - `delete_contact` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-contact.md - `delete_contact_note` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-contact-note.md - `delete_contact_task` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-contact-task.md - `delete_conversation` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-conversation.md - `delete_coupon` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-coupon.md - `delete_custom_provider_integration` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-custom-provider-integration.md - `delete_email_template` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-email-template.md - `delete_invoice_template` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-invoice-template.md - `delete_location` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-location.md - `delete_location_custom_field` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-location-custom-field.md - `delete_location_custom_value` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-location-custom-value.md - `delete_location_tag` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-location-tag.md - `delete_location_template` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-location-template.md - `delete_media_file` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-media-file.md - `delete_object_record` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-object-record.md - `delete_opportunity` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-opportunity.md - `delete_social_account` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-social-account.md - `delete_social_post` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/delete-social-post.md - `ghl_delete_association` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/ghl-delete-association.md - `ghl_delete_custom_field` — Destructive — https://policylayer.com/tools/thinkbedo-gohighlevel-mcp/ghl-delete-custom-field.md - …and 224 more: https://policylayer.com/tools/thinkbedo-gohighlevel-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=thinkbedo-gohighlevel-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/thinkbedo-gohighlevel-mcp