update_object_schema
Update object schema properties including labels, description, and searchable fields
This record as markdown: /tools/ghl/update-object-schema.md
What update_object_schema does on Ghl
AI agents use update_object_schema 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 | Object key to update |
labels | object | — | Updated singular and plural names (optional) |
locationId | string | — | Location ID (uses default if not provided) |
description | string | — | Updated description |
searchableProperties | array | Yes | Array of field keys that should be searchable (e.g., ["custom_objects.pet.name", "custom_objects.pet.breed"]) |
Parameters from the server's own tool schema.
Why update_object_schema is rated Medium
This tool modifies system/object configuration (labels, descriptions, searchable fields) which affects how data is organized and queried, but does not directly create, delete, or execute arbitrary operations. It is a reversible Write operation that changes object definitions rather than data instances.
From the tool's definition Tool updates 'object schema properties including labels, description, and searchable fields' — modifying metadata and configuration of data objects.
Attacks that exploit this kind of access
The rule that runs update_object_schema 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 update_object_schema, this is the rule to start with:
update_object_schema 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 update_object_schema call is checked against it from then on.
Questions about update_object_schema
Update object schema properties including labels, description, and searchable fields. 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.
update_object_schema 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 update_object_schema: 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.
update_object_schema 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 update_object_schema 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 update_object_schema. 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.
update_object_schema 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.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue