This record as markdown: /tools/aiwerk-mcp-server-ghl/custom-fields-create-custom-field.md
What custom_fields_create_custom_field does on Ghl
AI agents use custom_fields_create_custom_field to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Field name |
options | array | — | Options for the field (Optional, valid only for SINGLE_OPTIONS, MULTIPLE_OPTIONS, RADIO, CHECKBOX, TEXTBOX_LIST type) |
dataType | string | Yes | Type of field that you are trying to create |
fieldKey | string | Yes | Field key. For Custom Object it's formatted as "custom_object.{objectKey}.{fieldKey}". "custom_object" is a fixed prefix, "{objectKey}" is your custom object's |
parentId | string | Yes | ID of the parent folder |
objectKey | string | Yes | The key for your custom object. This key uniquely identifies the custom object. Example: "custom_object.pet" for a custom object related to pets. |
locationId | string | — | Location Id Defaults to GHL_LOCATION_ID when omitted. |
description | string | — | Description of the field |
placeholder | string | — | Placeholder text for the field |
showInForms | boolean | Yes | Whether the field should be shown in forms |
maxFileLimit | number | — | Maximum file limit for uploads. Applicable only for fields with a data type of FILE_UPLOAD. |
acceptedFormats | string | — | Allowed file formats for uploads. Options include: .pdf, .docx, .doc, .jpg, .jpeg, .png, .gif, .csv, .xlsx, .xls, all |
Parameters from the server's own tool schema.
Why custom_fields_create_custom_field is rated Medium
An AI agent can call custom_fields_create_custom_field faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs custom_fields_create_custom_field 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 custom_fields_create_custom_field, this is the rule to start with:
custom_fields_create_custom_field stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 custom_fields_create_custom_field call is checked against it from then on.
Questions about custom_fields_create_custom_field
Create Custom Field. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
custom_fields_create_custom_field accepts 12 parameters: name, options, dataType, fieldKey, parentId, objectKey, locationId, description, placeholder, showInForms, maxFileLimit, acceptedFormats. Required: dataType, fieldKey, parentId, objectKey, showInForms. 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 custom_fields_create_custom_field: 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.
custom_fields_create_custom_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the custom_fields_create_custom_field 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 custom_fields_create_custom_field. 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.
custom_fields_create_custom_field is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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