Get details of a specific calendar event
AI agents call get-event 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 event details from a calendar without creating, modifying, deleting, or executing operations. It is a straightforward read operation with minimal blast radius if misused—worst case, an AI agent gains access to calendar event information that the authenticated user already has access to.
From the tool's definition Tool name 'get-event' and description 'Get details of a specific calendar event' indicate data retrieval without modification. No side effects mentioned.
Attacks that exploit this kind of access
Get details of a specific calendar event. 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-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 Calendar MCP Server. Nothing to install.
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 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 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.
get-event is provided by the Google Calendar MCP Server MCP server (progrmoiz/cal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get-event is one line of Google Calendar MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →