get_calendar_events
Get appointments/events from calendars within a date range
This record as markdown: /tools/ghl/get-calendar-events.md
What get_calendar_events does on Ghl
AI agents call get_calendar_events 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 |
|---|---|---|---|
userId | string | — | Filter events by assigned user ID |
endTime | string | Yes | End time in milliseconds or ISO date (e.g., "2024-01-31" or "1706745599999") |
groupId | string | — | Filter events by calendar group ID |
startTime | string | Yes | Start time in milliseconds or ISO date (e.g., "2024-01-01" or "1704067200000") |
calendarId | string | — | Filter events by specific calendar ID |
Parameters from the server's own tool schema.
Why get_calendar_events is rated Low
This tool retrieves calendar events without modifying, deleting, or executing any operations. It has no side effects and only queries existing data within a specified date range, fitting the definition of a Read operation.
From the tool's definition The tool 'get_calendar_events' with description 'Get appointments/events from calendars within a date range' explicitly uses the retrieval verb 'Get' and performs a query operation to retrieve calendar data.
Attacks that exploit this kind of access
The rule that runs get_calendar_events 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_calendar_events, this is the rule to start with:
get_calendar_events 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_calendar_events call is checked against it from then on.
Questions about get_calendar_events
Get appointments/events from calendars within a date range. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_calendar_events accepts 5 parameters: userId, endTime, groupId, startTime, calendarId. Required: endTime, startTime. 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_calendar_events: 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_calendar_events 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_calendar_events 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_calendar_events. 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_calendar_events 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