This record as markdown: /tools/aiwerk-mcp-server-ghl/calendars-get-all-schedules.md
What calendars_get_all_schedules does on Ghl
AI agents call calendars_get_all_schedules 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 |
|---|---|---|---|
skip | number | — | Number of items to skip for pagination |
limit | number | — | Maximum number of items to return (max 500) |
userId | string | Yes | User ID to filter schedules by specific user |
calendarId | string | — | Calendar ID for filtering schedules by specific calendar |
locationId | string | — | Location ID to filter schedules by Defaults to GHL_LOCATION_ID when omitted. |
Parameters from the server's own tool schema.
Why calendars_get_all_schedules is rated Low
Even though calendars_get_all_schedules only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs calendars_get_all_schedules 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 calendars_get_all_schedules, this is the rule to start with:
calendars_get_all_schedules 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 calendars_get_all_schedules call is checked against it from then on.
Questions about calendars_get_all_schedules
List user availability schedule. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
calendars_get_all_schedules accepts 5 parameters: skip, limit, userId, calendarId, locationId. Required: userId. 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 calendars_get_all_schedules: 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.
calendars_get_all_schedules 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 calendars_get_all_schedules 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 calendars_get_all_schedules. 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.
calendars_get_all_schedules is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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