create_location_custom_value

Create a new custom value for a location

SERVERGhl SOURCEghl-mcp-server

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ghl/create-location-custom-value.md

WHAT IT DOES

What create_location_custom_value does on Ghl

AI agents use create_location_custom_value to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.

Parameter	Type	Required	Description
`name`	string	Yes	Name of the custom value field
`value`	string	Yes	Value to assign
`locationId`	string	Yes	The location ID

Parameters from the server's own tool schema.

RISK

Why create_location_custom_value is rated Medium

This tool creates new custom value data, which is a reversible modification. While it does not permanently destroy or move money, creating custom values could impact location configurations and business logic. The severity is medium because misuse could create incorrect data entries or cluttered configurations, but the effects are reversible through updates or deletion.

From the tool's definition Tool name 'create_location_custom_value' and description 'Create a new custom value for a location' indicate creation of new data within a location entity in the GoHighLevel CRM system.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_location_custom_value 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 create_location_custom_value, this is the rule to start with:

create_location_custom_value Rate-limited

create_location_custom_value stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_location_custom_value": {
      "limits": [
        {
          "counter": "create_location_custom_value_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every create_location_custom_value call is checked against it from then on.

FAQ

Questions about create_location_custom_value

What does the create_location_custom_value tool do? +

Create a new custom value for a location. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_location_custom_value accept? +

create_location_custom_value accepts 3 parameters: name, value, locationId. Required: name, value, locationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_location_custom_value? +

Register the Ghl MCP server in PolicyLayer and add a rule for create_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 Ghl. Nothing to install.

What risk level is create_location_custom_value? +

create_location_custom_value is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_location_custom_value? +

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

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

create_location_custom_value 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.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 253 Ghl tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →