delete-custom-field-2
Delete Custom Field
This record as markdown: /tools/drausal-gohighlevel-mcp/delete-custom-field-2.md
What delete-custom-field-2 does on GoHighLevel MCP Server
AI agents call delete-custom-field-2 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 delete-custom-field-2 is rated Critical
Deleting custom fields in a business management system like GoHighLevel results in irreversible data loss. Custom fields often contain important business data, and deletion cannot be undone without restoration from backups. This qualifies as Destructive rather than Write (which is reversible) due to the permanent nature of the operation.
From the tool's definition Tool name 'delete-custom-field-2' with description 'Delete Custom Field' explicitly performs a delete operation on custom field data.
Attacks that exploit this kind of access
The rule that runs delete-custom-field-2 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-custom-field-2, this is the rule to start with:
delete-custom-field-2 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every delete-custom-field-2 call is checked against it from then on.
Questions about delete-custom-field-2
Delete 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.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for delete-custom-field-2: 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.
delete-custom-field-2 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 delete-custom-field-2 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 delete-custom-field-2. 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.
delete-custom-field-2 is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
Across the catalogue