# 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/keshigami-ghl-mcp-workiong/ghl-get-custom-field-by-id ## Facts - Tool: `ghl_get_custom_field_by_id` - Server: GoHighLevel MCP Server (`keshigami/ghl-mcp-workiong`) — https://policylayer.com/tools/keshigami-ghl-mcp-workiong.md - Homepage: https://github.com/Keshigami/ghl-mcp-workiong - 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 custom field metadata by ID. It performs a query operation with no side effects, making it a Read category tool. The severity is low because retrieving field definitions poses minimal risk—the tool does not modify data, execute code, or trigger external actions. Confidence is high because the description is explicit about the retrieval-only nature of the operation. From the tool's own definition: "Tool name contains 'get' and description states 'Get a custom field or folder by its ID' with no mention of modification, deletion, or side effects." ## 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/keshigami-ghl-mcp-workiong/bulk-delete-social-posts.md - `cancel_scheduled_email` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/cancel-scheduled-email.md - `cancel_scheduled_message` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/cancel-scheduled-message.md - `delete_appointment` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-appointment.md - `delete_appointment_note` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-appointment-note.md - `delete_calendar` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-calendar.md - `delete_calendar_group` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-calendar-group.md - `delete_calendar_notification` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-calendar-notification.md - `delete_calendar_resource_equipment` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-calendar-resource-equipment.md - `delete_calendar_resource_room` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-calendar-resource-room.md - `delete_contact` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-contact.md - `delete_contact_note` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-contact-note.md - `delete_contact_task` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-contact-task.md - `delete_conversation` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-conversation.md - `delete_coupon` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-coupon.md - `delete_custom_provider_integration` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-custom-provider-integration.md - `delete_email_template` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-email-template.md - `delete_invoice_template` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-invoice-template.md - `delete_location` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-location.md - `delete_location_custom_field` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-location-custom-field.md - `delete_location_custom_value` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-location-custom-value.md - `delete_location_tag` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-location-tag.md - `delete_location_template` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-location-template.md - `delete_media_file` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-media-file.md - `delete_object_record` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-object-record.md - `delete_opportunity` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-opportunity.md - `delete_social_account` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-social-account.md - `delete_social_post` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/delete-social-post.md - `ghl_delete_association` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/ghl-delete-association.md - `ghl_delete_custom_field` — Destructive — https://policylayer.com/tools/keshigami-ghl-mcp-workiong/ghl-delete-custom-field.md - …and 224 more: https://policylayer.com/tools/keshigami-ghl-mcp-workiong.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=keshigami-ghl-mcp-workiong · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/keshigami-ghl-mcp-workiong