delete_custom_field

THE RISK

Critical Risk

Why delete_custom_field needs a policy

This tool removes custom fields from the GoHighLevel CRM system. Deletion of custom fields is irreversible and could cascade impact (data loss, broken workflows, form dependencies). While not system-critical like deleting all contacts, it represents permanent data structure modification. High severity due to potential business process disruption and data loss if triggered inappropriately by an AI agent.

From the tool's definition Tool name 'delete_custom_field' with description 'Delete a custom field' indicates irreversible deletion of data. The verb 'delete' is explicitly destructive.

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

POLICY

How to control delete_custom_field

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 delete_custom_field:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_custom_field"
  ]
}

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.

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GoHighLevel MCP Server tools

Destructive delete_appointment Delete an appointment Destructive delete_contact Delete a contact from GoHighLevel Destructive delete_contact_note Delete a note from a contact Destructive delete_contact_task Delete a task from a contact Destructive delete_custom_value Delete a custom value Destructive delete_opportunity Delete an opportunity from GoHighLevel Destructive delete_user Delete a user Destructive remove_contact_from_workflow Remove a contact from a workflow

All 64 GoHighLevel MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Govern database agents → Read-only defaults, blocked table drops, and no DELETE without a WHERE clause on every query.
Critical-risk tools in GoHighLevel MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about delete_custom_field

What does the delete_custom_field tool do? +

Delete a custom field. 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 delete_custom_field? +

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

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

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

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

delete_custom_field is provided by the GoHighLevel MCP Server MCP server (basicmachines-co/open-ghl-mcp). 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.

Start from GoHighLevel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →