This record as markdown: /tools/ghl/get-calendar-notifications.md
What get_calendar_notifications does on Ghl
AI agents call get_calendar_notifications to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
skip | number | — | Number to skip |
limit | number | — | Maximum number to return |
deleted | boolean | — | Include deleted notifications |
isActive | boolean | — | Filter by active status |
calendarId | string | Yes | Calendar ID |
Parameters from the server's own tool schema.
Why get_calendar_notifications is rated Low
This tool retrieves/queries calendar notification data without creating, modifying, or deleting any information. It is a pure read operation with minimal blast radius if misused by an agent—at worst, it exposes notification data the agent is already authorized to access.
From the tool's definition Tool name 'get_calendar_notifications' and description 'Get calendar notifications' indicate a retrieval operation with no modification capability.
Attacks that exploit this kind of access
The rule that runs get_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 get_calendar_notifications, this is the rule to start with:
get_calendar_notifications is read-only, so it stays allowed. 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 get_calendar_notifications call is checked against it from then on.
Questions about get_calendar_notifications
get_calendar_notifications is a read tool on the Ghl MCP server. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_calendar_notifications accepts 5 parameters: skip, limit, deleted, isActive, calendarId. Required: calendarId. 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 get_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.
get_calendar_notifications is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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