ghl_update_custom_field_folder

Update the name of an existing custom field folder.

SERVERGoHighLevel MCP Server SOURCEhooker-dev/hailey-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hooker-dev-hailey-mcp/ghl-update-custom-field-folder.md

What ghl_update_custom_field_folder does on GoHighLevel MCP Server

AI agents use ghl_update_custom_field_folder to create or update resources in GoHighLevel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.

Why ghl_update_custom_field_folder is rated Medium

This tool modifies an existing resource (renames a custom field folder) which is a reversible write operation. It has minimal blast radius as it only changes a folder name and does not affect the data within or delete anything.

From the tool's definition Update the name of an existing custom field folder

Questions about ghl_update_custom_field_folder

What does the ghl_update_custom_field_folder tool do? +

Update the name of an existing custom field folder. It is categorised as a Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ghl_update_custom_field_folder? +

Register the GoHighLevel MCP Server 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 GoHighLevel MCP Server. Nothing to install.

What risk level is ghl_update_custom_field_folder? +

ghl_update_custom_field_folder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ghl_update_custom_field_folder? +

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.

How do I block ghl_update_custom_field_folder completely? +

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.

What MCP server provides ghl_update_custom_field_folder? +

ghl_update_custom_field_folder is provided by the GoHighLevel MCP Server MCP server (hooker-dev/hailey-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GoHighLevel MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.