This record as markdown: /tools/ghl/create-calendar.md
What create_calendar does on Ghl
AI agents use create_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 | Yes | Name of the calendar |
groupId | string | — | Calendar group ID to organize the calendar |
isActive | boolean | — | Make calendar active immediately (default: true) |
autoConfirm | boolean | — | Automatically confirm appointments (default: true) |
description | string | — | Description of the calendar |
calendarType | string | Yes | Type of calendar to create |
slotDuration | number | — | Duration of appointment slots in minutes (default: 30) |
allowReschedule | boolean | — | Allow clients to reschedule appointments (default: true) |
slotDurationUnit | string | — | Unit for slot duration |
allowCancellation | boolean | — | Allow clients to cancel appointments (default: true) |
Parameters from the server's own tool schema.
Why create_calendar is rated Medium
This tool creates a new calendar, which is a reversible write operation. It does not retrieve data (Read), execute arbitrary code (Execute), delete data (Destructive), or involve financial transactions (Financial).
From the tool's definition Tool name 'create_calendar' and description 'Create a new calendar in GoHighLevel' indicate creation of a new calendar resource, which is a write operation that modifies the GoHighLevel system state.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs create_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 create_calendar, this is the rule to start with:
create_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 create_calendar call is checked against it from then on.
Questions about create_calendar
Create a new 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.
create_calendar accepts 10 parameters: name, groupId, isActive, autoConfirm, description, calendarType, slotDuration, allowReschedule, slotDurationUnit, allowCancellation. Required: name, calendarType. 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 create_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.
create_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 create_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 create_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.
create_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