list-calendar-event-instances
The occurrences of a recurring series, if the event is a series master. This property includes occurrences that are part of the recurrence pattern, and exceptions modified, but doesn't include occurrences canceled from the series. Navigation property. Read-only. Nullable. 💡 TIP: Expand a recurri...
This record as markdown: /tools/jo3zik-ms-365-mcp-server/list-calendar-event-instances.md
What list-calendar-event-instances does on Ms 365
AI agents call list-calendar-event-instances to retrieve information from Ms 365 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
top | number | — | Page size (Graph $top). Start small (e.g. 5–15) so responses fit the model context; raise only if needed. Use $select to return fewer fields per item. For more |
skip | number | — | Items to skip for pagination. Not supported with $search. |
count | boolean | — | Set true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains(). |
expand | array | — | Navigation properties to inline, e.g. attachments on a message or event. Only navigation properties can be expanded: expanding a non-navigation property such as |
filter | string | — | OData filter expression. Add $count=true for advanced filters (flag/flagStatus, contains()). Cannot combine with $search. |
search | string | — | KQL search query — wrap value in double quotes. Cannot combine with $filter. |
select | string | — | Comma-separated fields to return, e.g. id,subject,from,receivedDateTime |
eventId | string | Yes | Value for the 'eventId' path segment. Pass it under the name 'eventId', not as 'id'. Use the 'id' field of the event object as returned by Microsoft Graph. |
orderby | string | — | Sort expression, e.g. receivedDateTime desc |
timezone | string | — | IANA timezone name (e.g., "America/New_York", "Europe/London", "Asia/Tokyo") for calendar event times. If not specified, times are returned in UTC. |
calendarId | string | Yes | Value for the 'calendarId' path segment. Pass it under the name 'calendarId', not as 'id'. Use the 'id' field of the calendar object as returned by Microsoft Gr |
endDateTime | string | Yes | The end date and time of the time range, represented in ISO 8601 format. For example, 2019-11-08T20:00:00-08:00 |
Parameters from the server's own tool schema.
Why list-calendar-event-instances is rated Low
Even though list-calendar-event-instances only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (17 properties)
Attacks that exploit this kind of access
The rule that runs list-calendar-event-instances safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ms 365, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list-calendar-event-instances, this is the rule to start with:
list-calendar-event-instances is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ms 365, apply this rule, and every list-calendar-event-instances call is checked against it from then on.
Questions about list-calendar-event-instances
The occurrences of a recurring series, if the event is a series master. This property includes occurrences that are part of the recurrence pattern, and exceptions modified, but doesn't include occurrences canceled from the series. Navigation property. Read-only. Nullable. 💡 TIP: Expand a recurring event into individual instances within a date range. Requires startDateTime and endDateTime query parameters in ISO 8601 format (e.g., 2024-01-01T00:00:00Z). Use this to see all occurrences of a recurring event. It is categorised as a Read tool in the Ms 365 MCP Server, which means it retrieves data without modifying state.
list-calendar-event-instances accepts 12 parameters: top, skip, count, expand, filter, search, select, eventId, orderby, timezone, calendarId, endDateTime. Required: eventId, calendarId, endDateTime. The full parameter table on this page comes from the server's own tool schema.
Register the Ms 365 MCP server in PolicyLayer and add a rule for list-calendar-event-instances: 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 Ms 365. Nothing to install.
list-calendar-event-instances 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-event-instances 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-event-instances. 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-event-instances is provided by the Ms 365 MCP server (@jo3zik/ms-365-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ms 365, and thousands of servers like it.
This server
Across the catalogue