STEP 2 - Get events from a calendar. PREREQUISITE: You must first call list_calendars to get the calendarUrl. Returns events within the specified date range. Each event contains: url (needed for update/delete), etag (needed for delete), and data (iCalendar format with SUMMARY=title, DTSTART=start...
AI agents call list_events to retrieve information from Fastmail 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 and queries calendar events without making any changes to data. It has no side effects beyond reading event information. While calendar data could be considered sensitive personal information, the tool itself performs a straightforward read operation with limited blast radius if misused by an AI agent—it would only expose existing calendar data the user already has access to, not modify or delete…
From the tool's definition Tool description states it "Get events from a calendar" and "Returns events within the specified date range." No modification, deletion, or execution capabilities are mentioned. The tool is purely retrieving calendar event data.
Attacks that exploit this kind of access
STEP 2 - Get events from a calendar. PREREQUISITE: You must first call list_calendars to get the calendarUrl. Returns events within the specified date range. Each event contains: url (needed for update/delete), etag (needed for delete), and data (iCalendar format with SUMMARY=title, DTSTART=start time, DTEND=end time, LOCATION, DESCRIPTION). Parse the iCalendar data to show event details to the user. It is categorised as a Read tool in the Fastmail Calendar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fastmail Calendar MCP Server MCP server in PolicyLayer and add a rule for list_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 Fastmail Calendar MCP Server. Nothing to install.
list_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 list_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 list_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.
list_events is provided by the Fastmail Calendar MCP Server MCP server (nova-3951/fastmail-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 →