custom_fields_create_custom_field_folder
Create Custom Field Folder
This record as markdown: /tools/aiwerk-mcp-server-ghl/custom-fields-create-custom-field-folder.md
What custom_fields_create_custom_field_folder does on Ghl
AI agents use custom_fields_create_custom_field_folder 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 | Yes | Field name |
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. |
Parameters from the server's own tool schema.
Why custom_fields_create_custom_field_folder is rated Medium
An AI agent can call custom_fields_create_custom_field_folder 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.
Attacks that exploit this kind of access
The rule that runs custom_fields_create_custom_field_folder 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_folder, this is the rule to start with:
custom_fields_create_custom_field_folder 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_folder call is checked against it from then on.
Questions about custom_fields_create_custom_field_folder
Create Custom Field Folder. 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_folder accepts 3 parameters: name, objectKey, locationId. Required: name, objectKey. 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_folder: 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_folder 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_folder 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_folder. 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_folder 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