delete_location_custom_field
Delete a custom field from a location
This record as markdown: /tools/tailormadeweddings-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 custom field data associated with a location. This is an irreversible action that destroys stored information. While the blast radius is confined to custom field metadata rather than core business data (contacts, opportunities), deletion of fields that may be referenced by workflows, reports, or integrations could break dependent systems.
From the tool's definition Tool name explicitly uses 'delete' and description confirms it 'Delete a custom field from a location' — this irreversibly removes data that cannot be recovered through normal operations.
Attacks that exploit this kind of access
The rule that runs delete_location_custom_field 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_location_custom_field, this is the rule to start with:
delete_location_custom_field 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_location_custom_field call is checked against it from then on.
Questions about delete_location_custom_field
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.
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.
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.
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.
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.
delete_location_custom_field is provided by the GoHighLevel MCP Server MCP server (tailormadeweddings/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