delete_location_custom_field

Delete a custom field from a location

SERVERGoHighLevel MCP Server SOURCEhridayshah7/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/hridayshah7-gohighlevel-mcp/delete-location-custom-field.md

What delete_location_custom_field does on GoHighLevel MCP Server

AI agents call delete_location_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_location_custom_field is rated Critical

The tool permanently removes a custom field, which cannot be undone and may affect multiple records or workflows that depend on that field. This is a destructive operation with a high blast radius if executed unintentionally, as deleted fields and their associated data cannot be recovered.

From the tool's definition Tool name contains 'delete' and description states 'Delete a custom field from a location' - this is an irreversible deletion operation.

Questions about delete_location_custom_field

What does the delete_location_custom_field tool do? +

Delete a custom field from a location. 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_location_custom_field? +

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

delete_location_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_location_custom_field? +

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

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

delete_location_custom_field is provided by the GoHighLevel MCP Server MCP server (hridayshah7/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.