calendar_list_events
AI agents call calendar_list_events to retrieve information from Pyfastmail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries calendar data to return events, which is a non-destructive retrieval operation. The 'list' naming convention across the server's sibling tools confirms this pattern as Read-category. No description was provided, which slightly reduces confidence, but the name is unambiguous.
From the tool's definition Tool name 'calendar_list_events' indicates retrieval of calendar events with no modification capability. The 'list' pattern (consistent with sibling tools like 'calendar_list_calendars' and 'contacts_list') is a standard Read operation.
Attacks that exploit this kind of access
calendar_list_events. It is categorised as a Read tool in the Pyfastmail MCP Server, which means it retrieves data without modifying state.
Register the Pyfastmail MCP server in PolicyLayer and add a rule for calendar_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 Pyfastmail. Nothing to install.
calendar_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 calendar_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 calendar_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.
calendar_list_events is provided by the Pyfastmail MCP server (pjosols/pyfastmail-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 →