get_calendar
AI agents call get_calendar to retrieve information from Google Calendar MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calendar information with no modifications. The empty description and naming convention suggest it queries calendar metadata or properties, consistent with the Read category. Severity is low because calendar data exposure is typically not critical unless it contains highly sensitive scheduling information, but the default risk from reading calendar metadata alone is minimal.
From the tool's definition Tool name 'get_calendar' and sibling tools include 'list_calendars' and 'list_events' which are query/retrieval operations. The server description indicates 'calendar listing and event CRUD operations,' with retrieval as the primary non-destructive function.
Attacks that exploit this kind of access
get_calendar. It is categorised as a Read tool in the Google Calendar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Calendar MCP Server 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 Google Calendar MCP Server. 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 Google Calendar MCP Server MCP server (volodymyrkoval/fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →