get_calendar
Fetches one calendar-list entry: summary, description, timeZone (the calendar's default IANA zone — use it to interpret event times), accessRole, defaultReminders and primary. Works only for calendars on the user's list; for a shared calendar never added to the list, use raw_request with path cal...
This record as markdown: /tools/a1-x-tech-mcp-google-calendar/get-calendar.md
What get_calendar does on Mcp Google Calendar
AI agents call get_calendar to retrieve information from Mcp Google Calendar 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 |
|---|---|---|---|
calendar_id | string | Yes | The calendar id from list_calendars, or "primary" for the authenticated user's main calendar. |
Parameters from the server's own tool schema.
Why get_calendar is rated Low
Even though get_calendar 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
The rule that runs get_calendar safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Calendar, 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 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 Mcp Google Calendar, apply this rule, and every get_calendar call is checked against it from then on.
Questions about get_calendar
Fetches one calendar-list entry: summary, description, timeZone (the calendar's default IANA zone — use it to interpret event times), accessRole, defaultReminders and primary. Works only for calendars on the user's list; for a shared calendar never added to the list, use raw_request with path calendar/v3/calendars/<id> instead. It is categorised as a Read tool in the Mcp Google Calendar MCP Server, which means it retrieves data without modifying state.
get_calendar accepts 1 parameter: calendar_id. Required: calendar_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Calendar 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 Mcp Google Calendar. Nothing to install.
get_calendar 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 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. 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 is provided by the Mcp Google Calendar MCP server (@a1-x-tech/mcp-google-calendar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Calendar, and thousands of servers like it.
This server
Across the catalogue