This record as markdown: /tools/aiwerk-mcp-server-ghl/calendars-update-calendar.md
What calendars_update_calendar does on Ghl
AI agents use calendars_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 | — | |
slug | string | — | |
notes | string | — | |
formId | string | — | |
groupId | string | — | Group Id |
pixelId | string | — | |
isActive | boolean | — | |
eventType | string | — | |
guestType | string | — | |
openHours | array | — | |
preBuffer | number | — | Pre-Buffer is additional time that can be added before an appointment, allowing for extra time to get ready |
recurring | object | — |
Parameters from the server's own tool schema.
Why calendars_update_calendar is rated Medium
An AI agent can call calendars_update_calendar faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (58 properties)
Attacks that exploit this kind of access
The rule that runs calendars_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 calendars_update_calendar, this is the rule to start with:
calendars_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 calendars_update_calendar call is checked against it from then on.
Questions about calendars_update_calendar
Update Calendar. 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.
calendars_update_calendar accepts 12 parameters: name, slug, notes, formId, groupId, pixelId, isActive, eventType, guestType, openHours, preBuffer, recurring. 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 calendars_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.
calendars_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 calendars_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 calendars_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.
calendars_update_calendar is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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