AI agents call get_events to retrieve information from Calendar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_events retrieves calendar event data without modifying, creating, or deleting anything. It has no side effects and returns information only. Sibling tools like 'create_event', 'update_event', and 'delete_event' exist as separate tools, confirming this one is read-only. This is a standard data retrieval operation with minimal security risk.
From the tool's definition Tool name 'get_events' and sibling tools context (list_calendars, search_events, get_event, today, upcoming) indicate read-only retrieval. Server description confirms 'listing' as a core operation. Empty tool description lowers confidence slightly.
Attacks that exploit this kind of access
get_events. It is categorised as a Read tool in the Calendar MCP Server, which means it retrieves data without modifying state.
Register the Calendar 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. 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 MCP server (p-w-4-z/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 →