calendars_get_calendar_events

Get Calendar Events

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Low RISK CLASS

Category Read

Parameters 62 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/calendars-get-calendar-events.md

WHAT IT DOES

What calendars_get_calendar_events does on Ghl

AI agents call calendars_get_calendar_events 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
`userId`	string	—	User Id - Owner of an appointment. Either of userId, groupId or calendarId is required
`endTime`	string	Yes	End Time (in millis)
`groupId`	string	—	Either of groupId, calendarId or userId is required
`startTime`	string	Yes	Start Time (in millis)
`calendarId`	string	—	Either of calendarId, userId or groupId is required
`locationId`	string	—	Location Id Defaults to GHL_LOCATION_ID when omitted.

Parameters from the server's own tool schema.

RISK

Why calendars_get_calendar_events is rated Low

Even though calendars_get_calendar_events only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

calendars_get_calendar_events Allowed

calendars_get_calendar_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calendars_get_calendar_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about calendars_get_calendar_events

What does the calendars_get_calendar_events tool do? +

Get Calendar Events. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does calendars_get_calendar_events accept? +

calendars_get_calendar_events accepts 6 parameters: userId, endTime, groupId, startTime, calendarId, locationId. Required: endTime, startTime. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on calendars_get_calendar_events? +

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

calendars_get_calendar_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit calendars_get_calendar_events? +

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

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

calendars_get_calendar_events 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →