locations_get_custom_fields

Get Custom Fields

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/locations-get-custom-fields.md

WHAT IT DOES

What locations_get_custom_fields does on Ghl

AI agents call locations_get_custom_fields to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`model`	string	—	Model of the custom field you want to retrieve
`locationId`	string	—	Location Id Defaults to GHL_LOCATION_ID when omitted.

Parameters from the server's own tool schema.

RISK

Why locations_get_custom_fields is rated Low

Even though locations_get_custom_fields only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

locations_get_custom_fields Allowed

locations_get_custom_fields is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "locations_get_custom_fields": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about locations_get_custom_fields

What does the locations_get_custom_fields tool do? +

Get Custom Fields. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does locations_get_custom_fields accept? +

locations_get_custom_fields accepts 2 parameters: model, locationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on locations_get_custom_fields? +

Register the Ghl MCP server in PolicyLayer and add a rule for locations_get_custom_fields: 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 locations_get_custom_fields? +

locations_get_custom_fields is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit locations_get_custom_fields? +

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

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

locations_get_custom_fields is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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 569 Ghl tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →