decline-calendar-event

SERVERMs 365 SOURCE@jo3zik/ms-365-mcp-server

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jo3zik-ms-365-mcp-server/decline-calendar-event.md

WHAT IT DOES

What decline-calendar-event does on Ms 365

AI agents use decline-calendar-event to create or update resources in Ms 365, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ms 365 environment.

Parameter	Type	Required	Description
`body`	object	Yes
`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.

RISK

Why decline-calendar-event is rated Medium

An AI agent can call decline-calendar-event faster than any human can review: one bad instruction and it creates or modifies resources in Ms 365 by the hundred, each call as confident as the last.

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs decline-calendar-event 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 decline-calendar-event, this is the rule to start with:

decline-calendar-event Rate-limited

decline-calendar-event stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "decline-calendar-event": {
      "limits": [
        {
          "counter": "decline-calendar-event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ms 365, apply this rule, and every decline-calendar-event call is checked against it from then on.

FAQ

Questions about decline-calendar-event

What does the decline-calendar-event tool do? +

Decline invitation to the specified event in a user calendar. If the event allows proposals for new times, on declining the event, an invitee can choose to suggest an alternative time by including the proposedNewTime parameter. For more information on how to propose a time, and how to receive and accept a new time proposal, see Propose new meeting times. 💡 TIP: Declines a meeting invitation. Optional body: { sendResponse: true, comment: 'Cannot attend, conflict.' }. The event remains in the calendar as declined unless the user deletes it. It is categorised as a Write tool in the Ms 365 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does decline-calendar-event accept? +

decline-calendar-event accepts 5 parameters: body, confirm, eventId, includeHeaders, excludeResponse. Required: body, eventId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on decline-calendar-event? +

Register the Ms 365 MCP server in PolicyLayer and add a rule for decline-calendar-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 Ms 365. Nothing to install.

What risk level is decline-calendar-event? +

decline-calendar-event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit decline-calendar-event? +

Yes. Add a rate_limit block to the decline-calendar-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.

How do I block decline-calendar-event completely? +

Set action: deny in the PolicyLayer policy for decline-calendar-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.

What MCP server provides decline-calendar-event? +

decline-calendar-event 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.

KEEP EXPLORING

More on Ms 365, and thousands of servers like it.

This server

All 194 Ms 365 tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →