This record as markdown: /tools/ghl/update-appointment.md
What update_appointment does on Ghl
AI agents use update_appointment 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 |
|---|---|---|---|
title | string | — | Updated title/subject of the appointment |
address | string | — | Updated meeting location or address |
endTime | string | — | Updated end time in ISO format |
toNotify | boolean | — | Send notifications for this update |
startTime | string | — | Updated start time in ISO format |
appointmentId | string | Yes | The unique ID of the appointment to update |
assignedUserId | string | — | Updated assigned user ID |
appointmentStatus | string | — | Updated status of the appointment |
Parameters from the server's own tool schema.
Why update_appointment is rated Medium
The tool creates or modifies data reversibly—updating an appointment can be undone by changing it again. This is a Write operation, not Destructive (appointments aren't deleted, merely modified). The medium severity reflects that incorrect appointment updates could disrupt scheduling, notifications, or business operations, but the effect is contained to individual appointments and reversible.
From the tool's definition Tool name 'update_appointment' with description 'Update an existing appointment in GoHighLevel' indicates modification of existing data (appointment records).
Attacks that exploit this kind of access
The rule that runs update_appointment 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_appointment, this is the rule to start with:
update_appointment 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_appointment call is checked against it from then on.
Questions about update_appointment
Update an existing appointment in GoHighLevel. 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_appointment accepts 8 parameters: title, address, endTime, toNotify, startTime, appointmentId, assignedUserId, appointmentStatus. Required: appointmentId. 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_appointment: 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_appointment 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_appointment 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_appointment. 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_appointment 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