New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete-custom-field

<div> <p> Delete Custom Field By Id </p> <div> <span style=

SERVERGoHighLevel MCP Server SOURCEdrausal/gohighlevel-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/drausal-gohighlevel-mcp/delete-custom-field.md

What delete-custom-field does on GoHighLevel MCP Server

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

Why delete-custom-field is rated Critical

This tool permanently removes a custom field from the GoHighLevel system. Deletion is irreversible and could impact data integrity across contacts, opportunities, and workflows that rely on that field. While not as critical as deleting primary records, the destructive nature and potential cascading effects warrant high severity.

From the tool's definition Tool name 'delete-custom-field' explicitly performs deletion of a custom field by ID. The verb 'delete' indicates irreversible removal of data.

Questions about delete-custom-field

What does the delete-custom-field tool do? +

<div> <p> Delete Custom Field By Id </p> <div> <span style=. 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 (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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.