Get full details of a calendar event.
AI agents call ms365_get_event 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 event details without side effects. It is a read-only operation that queries existing data from the Microsoft Graph API. No data is created, modified, deleted, or used to trigger external actions. The low severity reflects minimal risk—disclosure of calendar event details poses limited threat compared to tools that execute actions, delete data, or move money.
From the tool's definition Tool name 'ms365_get_event' and description 'Get full details of a calendar event' indicate retrieval of calendar event data with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get full details of a calendar event. 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_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 Microsoft 365 MCP Server. Nothing to install.
ms365_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 ms365_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 ms365_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.
ms365_get_event 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 →