This record as markdown: /tools/ghl/disable-calendar-group.md
What disable_calendar_group does on Ghl
AI agents use disable_calendar_group 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 |
|---|---|---|---|
groupId | string | Yes | Calendar group ID |
isActive | boolean | Yes | Whether to enable (true) or disable (false) the group |
Parameters from the server's own tool schema.
Why disable_calendar_group is rated Medium
This tool creates or modifies data (calendar group status) reversibly. It does not delete, execute arbitrary code, or move money. The context of GoHighLevel (a CRM/sales platform) and sibling tools (contact management, campaigns, workflows) confirms this is state mutation. Severity is medium because misconfiguration could disrupt team scheduling and workflow visibility, but effects are reversible via re-enabling.
From the tool's definition 'Enable or disable a calendar group' — modifies the state of a calendar group configuration, reversibly toggling its active/inactive status without deletion.
Attacks that exploit this kind of access
The rule that runs disable_calendar_group 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 disable_calendar_group, this is the rule to start with:
disable_calendar_group 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 disable_calendar_group call is checked against it from then on.
Questions about disable_calendar_group
Enable or disable a calendar group. 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.
disable_calendar_group accepts 2 parameters: groupId, isActive. Required: groupId, isActive. 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 disable_calendar_group: 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.
disable_calendar_group 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 disable_calendar_group 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 disable_calendar_group. 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.
disable_calendar_group 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