This record as markdown: /tools/ghl/create-calendar-notifications.md
What create_calendar_notifications does on Ghl
AI agents use create_calendar_notifications 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 |
|---|---|---|---|
calendarId | string | Yes | Calendar ID |
notifications | array | Yes | Array of notification configurations |
Parameters from the server's own tool schema.
Why create_calendar_notifications is rated Medium
This tool creates new calendar notification entries, which is a reversible write operation. It adds data to the system without permanently deleting or destroying anything. Severity is medium because misuse could spam a user with unwanted notifications, but the effects are reversible (notifications can be deleted/dismissed).
From the tool's definition Tool name 'create_calendar_notifications' and description 'Create calendar notifications' indicate creating/writing new notification records in a calendar system.
Risk signalsAccepts raw HTML/template content (notifications[].body)
Attacks that exploit this kind of access
The rule that runs create_calendar_notifications 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 create_calendar_notifications, this is the rule to start with:
create_calendar_notifications 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 create_calendar_notifications call is checked against it from then on.
Questions about create_calendar_notifications
create_calendar_notifications is a write tool on the Ghl MCP server. 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.
create_calendar_notifications accepts 2 parameters: calendarId, notifications. Required: calendarId, notifications. 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 create_calendar_notifications: 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.
create_calendar_notifications 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 create_calendar_notifications 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 create_calendar_notifications. 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.
create_calendar_notifications 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