calendars_update_event_notification

Update notification

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/calendars-update-event-notification.md

WHAT IT DOES

What calendars_update_event_notification does on Ghl

AI agents use calendars_update_event_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	—	Body for email notification. Not necessary for in-App notification
`channel`	string	—	Notification channel
`deleted`	boolean	—	Marks the notification as deleted (soft delete)
`subject`	string	—	Subject for email notification. Not necessary for in-App notification
`fromName`	string	—	From name for email/sms notification
`isActive`	boolean	—	Is the notification active
`afterTime`	array	—	Specifies the time after which the follow-up notification should be sent. This is not required for other notification types.
`beforeTime`	array	—	Specifies the time before which the reminder notification should be sent. This is not required for other notification types.
`calendarId`	string	Yes
`fromNumber`	string	—	from number for sms notification
`templateId`	string	—	Template ID for email notification
`fromAddress`	string	—	From address for email notification

Parameters from the server's own tool schema.

RISK

Why calendars_update_event_notification is rated Medium

An AI agent can call calendars_update_event_notification 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.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

calendars_update_event_notification Rate-limited

calendars_update_event_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": {
    "calendars_update_event_notification": {
      "limits": [
        {
          "counter": "calendars_update_event_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 calendars_update_event_notification call is checked against it from then on.

FAQ

Questions about calendars_update_event_notification

What does the calendars_update_event_notification tool do? +

Update notification. 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 calendars_update_event_notification accept? +

calendars_update_event_notification accepts 12 parameters: body, channel, deleted, subject, fromName, isActive, afterTime, beforeTime, calendarId, fromNumber, templateId, fromAddress. Required: calendarId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on calendars_update_event_notification? +

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

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

Can I rate-limit calendars_update_event_notification? +

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

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

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

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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