This record as markdown: /tools/ghl/update-calendar.md
What update_calendar does on Ghl
AI agents use update_calendar 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 |
|---|---|---|---|
name | string | — | Updated name of the calendar |
isActive | boolean | — | Updated active status |
calendarId | string | Yes | The unique ID of the calendar to update |
autoConfirm | boolean | — | Updated auto-confirm setting |
description | string | — | Updated description of the calendar |
slotDuration | number | — | Updated duration of appointment slots in minutes |
allowReschedule | boolean | — | Updated reschedule permission setting |
allowCancellation | boolean | — | Updated cancellation permission setting |
Parameters from the server's own tool schema.
Why update_calendar is rated Medium
This tool modifies calendar data reversibly within GoHighLevel. It falls into the Write category since it creates or modifies data without permanent deletion. Severity is medium because calendar updates could affect scheduling and business operations, but changes are typically reversible through subsequent updates.
From the tool's definition Tool name is 'update_calendar' and description states 'Update an existing calendar in GoHighLevel'. The verb 'update' indicates modification of existing data rather than deletion or destruction.
Attacks that exploit this kind of access
The rule that runs update_calendar 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_calendar, this is the rule to start with:
update_calendar 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_calendar call is checked against it from then on.
Questions about update_calendar
Update an existing calendar 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_calendar accepts 8 parameters: name, isActive, calendarId, autoConfirm, description, slotDuration, allowReschedule, allowCancellation. Required: calendarId. 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_calendar: 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_calendar 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_calendar 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_calendar. 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_calendar 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