Retrieves all scheduled events and appointments from Google Calendar for a designated date.
AI agents call google_calendar_get_events to retrieve information from ContextCore MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves calendar data without creating, modifying, or deleting any events. It has no side effects beyond data retrieval. The blast radius of misuse is minimal—an attacker could see the user's calendar schedule but cannot alter it or access sensitive external systems. Classified as Read with low severity.
From the tool's definition Tool description states 'Retrieves all scheduled events and appointments from Google Calendar' — a read-only operation with no modification or deletion capability.
Attacks that exploit this kind of access
Retrieves all scheduled events and appointments from Google Calendar for a designated date. It is categorised as a Read tool in the ContextCore MCP MCP Server, which means it retrieves data without modifying state.
Register the ContextCore MCP server in PolicyLayer and add a rule for google_calendar_get_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 ContextCore MCP. Nothing to install.
google_calendar_get_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 google_calendar_get_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 google_calendar_get_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.
google_calendar_get_events is provided by the ContextCore MCP server (rkpraveendev/contextcore-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 →