get_free_slots
Get available time slots for booking appointments on a specific calendar
This record as markdown: /tools/ghl/get-free-slots.md
What get_free_slots does on Ghl
AI agents call get_free_slots 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 | — | Specific user ID to check availability for |
endDate | string | Yes | End date for availability check (YYYY-MM-DD format or milliseconds) |
timezone | string | — | Timezone for the results (e.g., "America/New_York") |
startDate | string | Yes | Start date for availability check (YYYY-MM-DD format or milliseconds) |
calendarId | string | Yes | The calendar ID to check availability for |
Parameters from the server's own tool schema.
Why get_free_slots is rated Low
This is a read-only operation that queries and returns calendar availability information. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could only retrieve scheduling information that is typically intended to be customer-facing. No financial transactions, destructive actions, or code execution are involved.
From the tool's definition Tool explicitly retrieves available time slots without modifying calendar data. Description states 'Get available time slots' indicating a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_free_slots 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_free_slots, this is the rule to start with:
get_free_slots 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_free_slots call is checked against it from then on.
Questions about get_free_slots
Get available time slots for booking appointments on a specific calendar. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_free_slots accepts 5 parameters: userId, endDate, timezone, startDate, calendarId. Required: endDate, startDate, calendarId. 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_free_slots: 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_free_slots 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_free_slots 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_free_slots. 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_free_slots 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