List Microsoft calendar events between two ISO timestamps.
AI agents call microsoft_calendar_events to retrieve information from Personal Mail 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 a specified time range. The verb 'list' and the read-only nature of querying calendar data without modifying, deleting, or executing actions places it squarely in the Read category. The severity is low because exposure of calendar events carries minimal risk compared to destructive or financial operations, though calendar data may have some privacy sensitivity.
From the tool's definition Tool name 'microsoft_calendar_events' and description 'List Microsoft calendar events between two ISO timestamps' indicates a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List Microsoft calendar events between two ISO timestamps. It is categorised as a Read tool in the Personal Mail MCP Server, which means it retrieves data without modifying state.
Register the Personal Mail MCP server in PolicyLayer and add a rule for microsoft_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 Personal Mail. Nothing to install.
microsoft_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 microsoft_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 microsoft_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.
microsoft_calendar_events is provided by the Personal Mail MCP server (srogerf/personal-mail-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 →