objects_update_custom_object
Update Object Schema By Key / Id
This record as markdown: /tools/aiwerk-mcp-server-ghl/objects-update-custom-object.md
What objects_update_custom_object does on Ghl
AI agents use objects_update_custom_object 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 |
|---|---|---|---|
key | string | Yes | key of the custom or standard object. For custom objects, the key must include the prefix “custom_objects.”. This key can be found on the Object Details page un |
labels | object | — | This is how your custom object will be displayed |
locationId | string | — | location id Defaults to GHL_LOCATION_ID when omitted. |
description | string | null | — | Pet Object`s description |
searchableProperties | array | Yes | Searchable Fields: Provide the field key of your object that you want to search on, using the format (custom_object.<object_name>.<field_key>). |
Parameters from the server's own tool schema.
Why objects_update_custom_object is rated Medium
An AI agent can call objects_update_custom_object faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs objects_update_custom_object 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 objects_update_custom_object, this is the rule to start with:
objects_update_custom_object 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every objects_update_custom_object call is checked against it from then on.
Questions about objects_update_custom_object
Update Object Schema By Key / Id. 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.
objects_update_custom_object accepts 5 parameters: key, labels, locationId, description, searchableProperties. Required: key, searchableProperties. 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 objects_update_custom_object: 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.
objects_update_custom_object is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the objects_update_custom_object 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 objects_update_custom_object. 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.
objects_update_custom_object 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.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue