ms365_list_events
AI agents call ms365_list_events to retrieve information from Microsoft 365 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 events without modifying them. Listed events are accessible data with no side effects. However, confidence is moderate (0.75) rather than high because the tool description is empty, leaving some ambiguity. The medium severity reflects that calendar data can be sensitive personal information, but Read operations have lower blast radius than Write or Execute actions.
From the tool's definition Tool name 'ms365_list_events' indicates a listing/query operation. Sibling tools like 'ms365_list_emails', 'ms365_list_mail_folders', and 'ms365_list_calendars' are all Read operations, establishing the pattern.
Attacks that exploit this kind of access
ms365_list_events. It is categorised as a Read tool in the Microsoft 365 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Microsoft 365 MCP Server MCP server in PolicyLayer and add a rule for ms365_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 Microsoft 365 MCP Server. Nothing to install.
ms365_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 ms365_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 ms365_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.
ms365_list_events is provided by the Microsoft 365 MCP Server MCP server (ronaldzuniga/ms365-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 →