update_calendar_notification

A write tool on the Ghl MCP server.

SERVERGhl SOURCEghl-mcp-server

Medium RISK CLASS

Category Write

Parameters 102 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ghl/update-calendar-notification.md

WHAT IT DOES

What update_calendar_notification does on Ghl

AI agents use update_calendar_notification 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
`body`	string	—	Notification body
`channel`	string	—	Notification channel
`deleted`	boolean	—	Whether notification is deleted
`subject`	string	—	Notification subject
`isActive`	boolean	—	Whether notification is active
`calendarId`	string	Yes	Calendar ID
`templateId`	string	—	Template ID
`receiverType`	string	—	Who receives the notification
`notificationId`	string	Yes	Notification ID
`notificationType`	string	—	Type of notification

Parameters from the server's own tool schema.

RISK

Why update_calendar_notification is rated Medium

This tool creates or modifies calendar notification data reversibly—it updates notification configurations without permanently deleting them. It falls under Write rather than Read (retrieves only) or Destructive (irreversible deletion).

From the tool's definition Tool name 'update_calendar_notification' indicates modification of an existing calendar notification setting.

Risk signalsAccepts raw HTML/template content (body) · High parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_calendar_notification 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 update_calendar_notification, this is the rule to start with:

update_calendar_notification Rate-limited

update_calendar_notification 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_calendar_notification": {
      "limits": [
        {
          "counter": "update_calendar_notification_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every update_calendar_notification call is checked against it from then on.

FAQ

Questions about update_calendar_notification

What does the update_calendar_notification tool do? +

update_calendar_notification 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 update_calendar_notification accept? +

update_calendar_notification accepts 10 parameters: body, channel, deleted, subject, isActive, calendarId, templateId, receiverType, notificationId, notificationType. Required: calendarId, notificationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_calendar_notification? +

Register the Ghl MCP server in PolicyLayer and add a rule for update_calendar_notification: 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 update_calendar_notification? +

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

Can I rate-limit update_calendar_notification? +

Yes. Add a rate_limit block to the update_calendar_notification 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 update_calendar_notification completely? +

Set action: deny in the PolicyLayer policy for update_calendar_notification. 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 update_calendar_notification? +

update_calendar_notification 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.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 253 Ghl tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP →calendar_create_event on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →