This record as markdown: /tools/ghl/delete-calendar-group.md
What delete_calendar_group does on Ghl
AI agents call delete_calendar_group to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
groupId | string | Yes | Calendar group ID |
Parameters from the server's own tool schema.
Why delete_calendar_group is rated Critical
This tool permanently deletes a calendar group, which is an irreversible operation that cannot be undone. Deletion of calendar groups could cause loss of scheduling infrastructure, associated events, or team coordination data. This fits the Destructive category as the primary harm vector.
From the tool's definition Tool name is 'delete_calendar_group' and description states 'Delete a calendar group'. The verb 'delete' combined with the scope of deleting an entire calendar group indicates irreversible data removal.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_calendar_group, this is the rule to start with:
delete_calendar_group is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every delete_calendar_group call is checked against it from then on.
Questions about delete_calendar_group
Delete a calendar group. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_calendar_group accepts 1 parameter: groupId. Required: groupId. 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 delete_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.
delete_calendar_group is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue