Get events from Google Calendar
AI agents call getEvents 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 events without side effects. While calendar data may contain personal information (meeting details, attendees, times), the read-only nature and typical use case of querying one's own calendar via authenticated OAuth2 results in low severity. The primary risk is data exposure if credentials are compromised, but that is not specific to this tool's function.
From the tool's definition Tool name 'getEvents' and description 'Get events from Google Calendar' indicate retrieval of calendar data with no modification or deletion.
Attacks that exploit this kind of access
Get events from Google 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 getEvents: 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.
getEvents 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 getEvents 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 getEvents. 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.
getEvents is provided by the Google Calendar MCP Server MCP server (naotaka3/google-calendar-mcp). 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 →