ghl_update_custom_field_folder
Update the name of an existing custom field folder.
This record as markdown: /tools/ghl/ghl-update-custom-field-folder.md
What ghl_update_custom_field_folder does on Ghl
AI agents use ghl_update_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 |
|---|---|---|---|
id | string | Yes | The ID of the folder to update |
name | string | Yes | New name for the folder |
locationId | string | — | GoHighLevel location ID (will use default if not provided) |
Parameters from the server's own tool schema.
Why ghl_update_custom_field_folder is rated Medium
This tool modifies metadata (a folder name) in a reversible manner. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely retrieve information (Read). Renaming a folder is a straightforward Write operation with low blast radius—an AI agent could at worst create confusion by renaming folders, but the action is easily undone.
From the tool's definition Tool description states 'Update the name of an existing custom field folder' — the 'update' verb combined with 'name' (metadata, not data deletion or irreversible change) clearly indicates a reversible modification operation.
Attacks that exploit this kind of access
The rule that runs ghl_update_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 ghl_update_custom_field_folder, this is the rule to start with:
ghl_update_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 ghl_update_custom_field_folder call is checked against it from then on.
Questions about ghl_update_custom_field_folder
Update the name of an existing 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.
ghl_update_custom_field_folder accepts 3 parameters: id, name, locationId. Required: id, name. 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_update_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.
ghl_update_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 ghl_update_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 ghl_update_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.
ghl_update_custom_field_folder 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