update_object_record

Update an existing record in a custom or standard object

SERVERGhl SOURCEghl-mcp-server

Medium RISK CLASS

Category Write

Parameters 62 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ghl/update-object-record.md

WHAT IT DOES

What update_object_record does on Ghl

AI agents use update_object_record 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
`owner`	array	—	Updated array of user IDs who own this record
`recordId`	string	Yes	ID of the record to update
`followers`	array	—	Updated array of user IDs who follow this record
`schemaKey`	string	Yes	Schema key of the object
`locationId`	string	—	Location ID (uses default if not provided)
`properties`	object	—	Updated record properties as key-value pairs

Parameters from the server's own tool schema.

RISK

Why update_object_record is rated Medium

This tool creates or modifies data in a reversible manner without deletion or financial transactions. The word 'Update' is the key indicator of a Write operation. Severity is medium because bulk updates across CRM records could affect many contacts/opportunities, but the operation is reversible (can be undone by updating again). Confidence is high because the description clearly states the tool updates records.

From the tool's definition Tool name 'update_object_record' and description 'Update an existing record in a custom or standard object' explicitly describe modifying data reversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_object_record Rate-limited

update_object_record 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_object_record": {
      "limits": [
        {
          "counter": "update_object_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about update_object_record

What does the update_object_record tool do? +

Update an existing record in a custom or standard object. 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.

What parameters does update_object_record accept? +

update_object_record accepts 6 parameters: owner, recordId, followers, schemaKey, locationId, properties. Required: recordId, schemaKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_object_record? +

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

update_object_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_object_record? +

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

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

update_object_record 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.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 253 Ghl tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →