This record as markdown: /tools/ghl/delete-location-custom-field.md
What delete_location_custom_field does on Ghl
AI agents call delete_location_custom_field to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
locationId | string | Yes | The location ID |
customFieldId | string | Yes | The custom field ID to delete |
Parameters from the server's own tool schema.
Why delete_location_custom_field is rated Critical
The tool performs an irreversible deletion operation on location custom fields. While not as broad in blast radius as deleting entire locations or contacts, deletion of custom fields cannot be undone and represents permanent data loss. This qualifies as Destructive (irreversibly deletes data) rather than Write (which is reversible).
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a custom field from a location' – this is an irreversible removal of data.
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 Ghl, 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 Ghl, 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 Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_location_custom_field accepts 2 parameters: locationId, customFieldId. Required: locationId, customFieldId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl 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 Ghl. 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 Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
Across the catalogue