custom_fields_get_custom_fields_by_object_key

Get Custom Fields By Object Key

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What custom_fields_get_custom_fields_by_object_key does on Ghl

AI agents call custom_fields_get_custom_fields_by_object_key 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
`objectKey`	string	Yes	key of the Object. Must include "custom_objects." prefix for custom objects. Available on the Custom Objects details Page under settings
`locationId`	string	—	Defaults to GHL_LOCATION_ID when omitted.

Parameters from the server's own tool schema.

RISK

Why custom_fields_get_custom_fields_by_object_key is rated Low

Even though custom_fields_get_custom_fields_by_object_key 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 custom_fields_get_custom_fields_by_object_key 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 custom_fields_get_custom_fields_by_object_key, this is the rule to start with:

custom_fields_get_custom_fields_by_object_key Allowed

custom_fields_get_custom_fields_by_object_key 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": {
    "custom_fields_get_custom_fields_by_object_key": {}
  }
}

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 custom_fields_get_custom_fields_by_object_key call is checked against it from then on.

FAQ

Questions about custom_fields_get_custom_fields_by_object_key

What does the custom_fields_get_custom_fields_by_object_key tool do? +

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

What parameters does custom_fields_get_custom_fields_by_object_key accept? +

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

How do I enforce a policy on custom_fields_get_custom_fields_by_object_key? +

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

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

Can I rate-limit custom_fields_get_custom_fields_by_object_key? +

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

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

custom_fields_get_custom_fields_by_object_key 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 →