tentatively-accept-event · Outlook MCP Server MCP

WHAT IT DOES

What tentatively-accept-event does on Outlook MCP Server

AI agents use tentatively-accept-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.

WHY IT NEEDS A POLICY

Why tentatively-accept-event needs a policy

The tool creates or modifies calendar event data (specifically the user's RSVP status) in a reversible manner. It does not delete data (not Destructive), does not move money (not Financial), and does not execute arbitrary code (not Execute). The severity is medium because misuse could create calendar confusion or unwanted commitments, but the action is fully reversible by changing the response status again.

From the tool's definition Tool performs 'tentatively accepts a calendar event invitation', which modifies the acceptance status of a calendar event. This is a state-changing operation on calendar data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tentatively-accept-event Rate-limited

tentatively-accept-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": {
    "tentatively-accept-event": {
      "limits": [
        {
          "counter": "tentatively-accept-event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Outlook MCP Server, so you can run agents against it safely.

FAQ

Questions about tentatively-accept-event

What does the tentatively-accept-event tool do? +

Tentatively accepts a calendar event invitation. 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.

How do I enforce a policy on tentatively-accept-event? +

Register the Outlook MCP Server MCP server in PolicyLayer and add a rule for tentatively-accept-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.

What risk level is tentatively-accept-event? +

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

Can I rate-limit tentatively-accept-event? +

Yes. Add a rate_limit block to the tentatively-accept-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 tentatively-accept-event completely? +

Set action: deny in the PolicyLayer policy for tentatively-accept-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 tentatively-accept-event? +

tentatively-accept-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.