dismiss-calendar-event-reminder
Dismiss a reminder that has been triggered for an event in a user calendar. 💡 TIP: Dismisses a triggered event reminder so it won't re-fire. No request body required. Pair with list-calendar-events or get-schedule to find active reminders.
This record as markdown: /tools/jo3zik-ms-365-mcp-server/dismiss-calendar-event-reminder.md
What dismiss-calendar-event-reminder does on Ms 365
AI agents call dismiss-calendar-event-reminder 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 |
|---|---|---|---|
confirm | boolean | — | For destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly app |
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. |
includeHeaders | boolean | — | Include response headers (including ETag) in the response metadata |
excludeResponse | boolean | — | Exclude the full response body and only return success or failure indication |
Parameters from the server's own tool schema.
Why dismiss-calendar-event-reminder is rated Low
Even though dismiss-calendar-event-reminder 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.
Attacks that exploit this kind of access
The rule that runs dismiss-calendar-event-reminder 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 dismiss-calendar-event-reminder, this is the rule to start with:
dismiss-calendar-event-reminder 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 dismiss-calendar-event-reminder call is checked against it from then on.
Questions about dismiss-calendar-event-reminder
Dismiss a reminder that has been triggered for an event in a user calendar. 💡 TIP: Dismisses a triggered event reminder so it won't re-fire. No request body required. Pair with list-calendar-events or get-schedule to find active reminders. It is categorised as a Read tool in the Ms 365 MCP Server, which means it retrieves data without modifying state.
dismiss-calendar-event-reminder accepts 4 parameters: confirm, eventId, includeHeaders, excludeResponse. Required: eventId. 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 dismiss-calendar-event-reminder: 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.
dismiss-calendar-event-reminder 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 dismiss-calendar-event-reminder 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 dismiss-calendar-event-reminder. 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.
dismiss-calendar-event-reminder 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