get_calendars
Get all calendars in the GoHighLevel location with optional filtering
This record as markdown: /tools/ghl/get-calendars.md
What get_calendars does on Ghl
AI agents call get_calendars to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
groupId | string | — | Filter calendars by group ID |
showDrafted | boolean | — | Include draft calendars (default: true) |
Parameters from the server's own tool schema.
Why get_calendars is rated Low
This tool retrieves calendar information from a GoHighLevel location. The verb 'Get' and the absence of any language suggesting modification, deletion, or execution means this is a straightforward read operation. No data is created, modified, deleted, or at risk of harm through querying calendars.
From the tool's definition Tool name 'get_calendars' and description 'Get all calendars in the GoHighLevel location with optional filtering' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_calendars 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 get_calendars, this is the rule to start with:
get_calendars is read-only, so it stays allowed. 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 get_calendars call is checked against it from then on.
Questions about get_calendars
Get all calendars in the GoHighLevel location with optional filtering. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_calendars accepts 2 parameters: groupId, showDrafted. 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 get_calendars: 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.
get_calendars is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_calendars 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 get_calendars. 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.
get_calendars 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