Delete a custom field by ID. This will permanently remove the field and its data.
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.
This tool irreversibly deletes data (custom field and all its values) and cannot be undone. Permanent data loss qualifies as Destructive rather than Write. The impact is high because deletion of a field cascades to all contacts/records using that field, affecting data integrity across the CRM system. High confidence due to explicit 'permanently remove' language in description.
From the tool's definition 'Delete a custom field by ID. This will permanently remove the field and its data.' - explicitly states permanent removal of field and associated data.
Attacks that exploit this kind of access
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.
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.
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.
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.
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.
ghl_delete_custom_field 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.
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 →