Get today's events from the primary calendar
AI agents call get_today_events 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 and queries calendar event data without creating, modifying, or deleting any entries. It has no side effects beyond reading information. The action is purely informational—fetching a user's schedule for a specific day. This is a straightforward Read operation with minimal risk to the user's calendar or systems.
From the tool's definition Tool name 'get_today_events' and description 'Get today's events from the primary calendar' indicate retrieval of calendar data with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get today's events from the primary 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_today_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 Google Calendar MCP Server. Nothing to install.
get_today_events 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_today_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.
Set action: deny in the PolicyLayer policy for get_today_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.
get_today_events is provided by the Google Calendar MCP Server MCP server (shameerpc5029/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 →