List calendar events within a date range (max 200 events).
AI agents call list_calendar_events to retrieve information from TrekMail 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 calendar event data within specified parameters. It performs a read-only query with no capacity to modify, delete, or execute operations. The maximum of 200 events returned is a reasonable safeguard. Exposure of calendar event metadata poses minimal risk if misused by an agent—it cannot alter infrastructure or trigger external actions.
From the tool's definition Tool name is 'list_calendar_events' and description states it 'List calendar events within a date range'; the verb 'list' and the retrieval semantics indicate data querying with no modification or side effects.
Attacks that exploit this kind of access
List calendar events within a date range (max 200 events). It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for list_calendar_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 TrekMail MCP Server. Nothing to install.
list_calendar_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_calendar_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_calendar_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_calendar_events is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). 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 →