get_calendar

Get detailed information about a specific calendar by ID

SERVERGhl SOURCEghl-mcp-server

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_calendar does on Ghl

AI agents call get_calendar 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
`calendarId`	string	Yes	The unique ID of the calendar to retrieve

Parameters from the server's own tool schema.

RISK

Why get_calendar is rated Low

The tool retrieves calendar data based on an ID parameter. There is no modification, deletion, execution, or financial impact. This is a straightforward read operation that queries existing data without mutation.

From the tool's definition Tool name is 'get_calendar' and description states 'Get detailed information about a specific calendar by ID' — this is a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_calendar Allowed

get_calendar 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": {
    "get_calendar": {}
  }
}

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 get_calendar call is checked against it from then on.

FAQ

Questions about get_calendar

What does the get_calendar tool do? +

Get detailed information about a specific calendar by ID. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does get_calendar accept? +

get_calendar accepts 1 parameter: calendarId. Required: calendarId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_calendar? +

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

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

Can I rate-limit get_calendar? +

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

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

get_calendar 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

get_ctf_calendar on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →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 →