AI agents call calendar_get_event to retrieve information from Google without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves event details without creating, modifying, deleting, or executing any operations. It is a straightforward query operation that returns existing data from a calendar, consistent with Read category tools like 'get' or 'fetch'. Low severity reflects minimal blast radius — an AI misusing this tool could only access calendar information the authenticated user already has access to.
From the tool's definition Tool name is 'calendar_get_event' and description states 'Get detailed information about a specific calendar event' — purely retrieval with no modifications or side effects.
Attacks that exploit this kind of access
Get detailed information about a specific calendar event. It is categorised as a Read tool in the Google MCP Server, which means it retrieves data without modifying state.
Register the Google MCP server in PolicyLayer and add a rule for calendar_get_event: 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. Nothing to install.
calendar_get_event 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 calendar_get_event 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 calendar_get_event. 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.
calendar_get_event is provided by the Google MCP server (psckeithw/mcp-google). 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 →