get_events
AI agents call get_events to retrieve information from Calendar App without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves calendar events, which is a read-only query operation with no side effects. The empty description prevents full certainty, but the context of a calendar access server focused on retrieval operations and the read-only nature of 'get_events' clearly indicates data retrieval. Low severity because unauthorized calendar viewing poses minimal immediate risk.
From the tool's definition Tool named 'get_events' on a calendar server with sibling tools focused on viewing, searching, and filtering calendar data. The server description emphasizes 'viewing, searching, and filtering' with no mention of modification capabilities.
Attacks that exploit this kind of access
get_events. It is categorised as a Read tool in the Calendar App MCP Server, which means it retrieves data without modifying state.
Register the Calendar App MCP server in PolicyLayer and add a rule for 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 Calendar App. Nothing to install.
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 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 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.
get_events is provided by the Calendar App MCP server (rygwdn/calendar-app-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 →