ghl_delete_custom_field_folder

Delete a custom field folder. This will also affect any fields within the folder.

Server GoHighLevel MCP Server thinkbedo/gohighlevel_mcp
Category Destructive
Risk class Critical
Parameters 00 required

What ghl_delete_custom_field_folder does on GoHighLevel MCP Server

AI agents call ghl_delete_custom_field_folder to permanently remove resources in GoHighLevel MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why ghl_delete_custom_field_folder needs a policy

This tool permanently removes a custom field folder and all associated fields within it. The deletion cannot be undone and affects both the folder and its contents, making it a destructive operation. While the blast radius is significant for data organization and configuration, it is scoped to field schema rather than customer/transaction data, warranting 'high' rather than 'critical' severity.

From the tool's definition Tool name contains 'delete' and description states 'Delete a custom field folder. This will also affect any fields within the folder.' The action is irreversible and impacts dependent data structures.

Questions about ghl_delete_custom_field_folder

What does the ghl_delete_custom_field_folder tool do? +

Delete a custom field folder. This will also affect any fields within the folder. It is categorised as a Destructive tool in the GoHighLevel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on ghl_delete_custom_field_folder? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for ghl_delete_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_delete_custom_field_folder? +

ghl_delete_custom_field_folder is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit ghl_delete_custom_field_folder? +

Yes. Add a rate_limit block to the ghl_delete_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_delete_custom_field_folder completely? +

Set action: deny in the PolicyLayer policy for ghl_delete_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_delete_custom_field_folder? +

ghl_delete_custom_field_folder is provided by the GoHighLevel MCP Server MCP server (thinkbedo/gohighlevel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.