create_calendar_notifications

A write tool on the Ghl MCP server.

SERVERGhl SOURCEghl-mcp-server
Medium RISK CLASS
Category Write
Parameters 22 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about create_calendar_notifications

What does the create_calendar_notifications tool do? +

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.

What parameters does create_calendar_notifications accept? +

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.

How do I enforce a policy on create_calendar_notifications? +

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.

What risk level is create_calendar_notifications? +

create_calendar_notifications is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_calendar_notifications? +

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.

How do I block create_calendar_notifications completely? +

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.

What MCP server provides create_calendar_notifications? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ghl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.