ghl_update_custom_field_folder · GoHighLevel MCP Server MCP

WHAT IT DOES

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 IT NEEDS A POLICY

Why ghl_update_custom_field_folder needs a policy

This tool modifies existing data (folder name) in a reversible manner typical of Write operations. The update can be undone by renaming again. It affects CRM configuration rather than core customer data, making it Write rather than Destructive.

From the tool's definition Tool description states it 'Update[s] the name of an existing custom field folder' — a direct modification operation that changes configuration metadata without deleting or reversing irreversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ghl_update_custom_field_folder Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ghl_update_custom_field_folder": {
      "limits": [
        {
          "counter": "ghl_update_custom_field_folder_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GoHighLevel MCP Server, so you can run agents against it safely.

FAQ

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 (thinkbedo/gohighlevel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.