Declines a calendar event
AI agents use decline-event to create or update resources in Outlook MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outlook MCP Server environment.
Declining an event modifies calendar state and may notify organizers/attendees, but the action is reversible (user can rescind declination or accept later). This is a Write-category operation rather than Execute because it targets a specific calendar object with a well-defined outcome, not arbitrary code execution.
From the tool's definition Tool explicitly performs 'decline-event' action on calendar events. Outlook calendar operations are listed as 'list, create, accept, decline, delete events'; this tool modifies event state (acceptance status) through a reversible operation.
Attacks that exploit this kind of access
Declines a calendar event. It is categorised as a Write tool in the Outlook MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Outlook MCP Server MCP server in PolicyLayer and add a rule for decline-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 Outlook MCP Server. Nothing to install.
decline-event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the decline-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 decline-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.
decline-event is provided by the Outlook MCP Server MCP server (peacockery-studio/outlook-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 →