This record as markdown: /tools/aiwerk-mcp-server-ghl/calendars-create-schedule.md
What calendars_create_schedule does on Ghl
AI agents use calendars_create_schedule to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Human-readable name for the schedule |
rules | array | — | Schedule rules defining when the schedule is active |
userId | string | Yes | User ID associated with the schedule |
timezone | string | Yes | Timezone for the schedule (IANA timezone identifier) |
locationId | string | — | Location ID where this schedule applies Defaults to GHL_LOCATION_ID when omitted. |
calendarIds | array | — | Calendar IDs associated with the schedule |
Parameters from the server's own tool schema.
Why calendars_create_schedule is rated Medium
An AI agent can call calendars_create_schedule faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs calendars_create_schedule 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_create_schedule, this is the rule to start with:
calendars_create_schedule stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_create_schedule call is checked against it from then on.
Questions about calendars_create_schedule
Create user availability schedule. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
calendars_create_schedule accepts 6 parameters: name, rules, userId, timezone, locationId, calendarIds. Required: name, userId, timezone. 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_create_schedule: 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_create_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the calendars_create_schedule 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_create_schedule. 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_create_schedule 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