delete_location_custom_value

Delete a custom value from a location

SERVERGoHighLevel MCP Server SOURCEhooker-dev/hailey-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/hooker-dev-hailey-mcp/delete-location-custom-value.md

What delete_location_custom_value does on GoHighLevel MCP Server

AI agents call delete_location_custom_value 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_value is rated Critical

The tool permanently removes custom data from a location record without option to undo. While not as critical as deleting entire locations or contacts, it destroys data irreversibly. Severity is 'high' rather than 'critical' because the blast radius is limited to a single custom value field rather than entire records or financial systems.

From the tool's definition Tool name 'delete_location_custom_value' uses 'delete' verb and description states 'Delete a custom value from a location'—this is an irreversible deletion operation.

Questions about delete_location_custom_value

What does the delete_location_custom_value tool do? +

Delete a custom value 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_value? +

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

delete_location_custom_value 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_value? +

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

Set action: deny in the PolicyLayer policy for delete_location_custom_value. 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_value? +

delete_location_custom_value is provided by the GoHighLevel MCP Server MCP server (hooker-dev/hailey-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.