Critical Risk →

ghl_delete_custom_field

Delete a custom field by ID. This will permanently remove the field and its data.

How to control ghl_delete_custom_field ↓

AI agents call ghl_delete_custom_field 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.

Critical Risk

This tool irreversibly deletes data and cannot be undone. Deletion of custom fields will destroy all associated data across potentially many records in the CRM system, making this a destructive operation with significant blast radius if misused by an AI agent.

From the tool's definition Tool name contains 'delete'; description explicitly states 'permanently remove the field and its data'

Documented attack patterns abuse exactly the kind of access ghl_delete_custom_field gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ghl_delete_custom_field:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "ghl_delete_custom_field"
  ]
}

ghl_delete_custom_field disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register GoHighLevel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the ghl_delete_custom_field tool do? +

Delete a custom field by ID. This will permanently remove the field and its data. 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? +

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

ghl_delete_custom_field 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? +

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

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

ghl_delete_custom_field is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GoHighLevel MCP Server tool call.

Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.