<div> <p> Get Custom Fields By Object Key</p> <div> <span style=
AI agents call get-custom-fields-by-object-key to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries custom field data indexed by an object key without side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because exposing custom field metadata poses minimal risk even if misused by an AI agent—it does not modify data, execute code, delete records, or move money.
From the tool's definition Tool name 'get-custom-fields-by-object-key' and description prefix 'Get Custom Fields By Object Key' indicate a retrieval operation that queries custom fields associated with an object identifier.
Documented attack patterns abuse exactly the kind of access get-custom-fields-by-object-key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-custom-fields-by-object-key:
{
"version": "1",
"default": "deny",
"tools": {
"get-custom-fields-by-object-key": {}
}
}get-custom-fields-by-object-key is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
<div> <p> Get Custom Fields By Object Key</p> <div> <span style=. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for 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 GoHighLevel MCP Server. Nothing to install.
get-custom-fields-by-object-key is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
get-custom-fields-by-object-key is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GoHighLevel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
406 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.