AI agents call calendar_get_event to retrieve information from M365 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 information, which is a read-only operation with no side effects. Even though the description is empty, the name clearly indicates data retrieval ('get_event'). The severity is low because retrieving calendar events poses minimal risk—it returns information the authenticated user already has access to, with no ability to modify, delete, or execute operations.
From the tool's definition Tool name 'calendar_get_event' indicates retrieval of calendar event data. The empty description limits specificity, but the naming convention and position alongside other read-like tools (calendar_check_availability) in a Microsoft 365 management context…
Attacks that exploit this kind of access
calendar_get_event. It is categorised as a Read tool in the M365 MCP Server, which means it retrieves data without modifying state.
Register the M365 MCP server in PolicyLayer and add a rule for calendar_get_event: 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 M365. Nothing to install.
calendar_get_event 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_get_event 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_get_event. 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_get_event is provided by the M365 MCP server (robin-collins/m365-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 →