tentatively-accept-event · Outlook Assistant MCP

WHAT IT DOES

What tentatively-accept-event does on Outlook Assistant

AI agents use tentatively-accept-event to create or update resources in Outlook Assistant — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outlook Assistant environment.

WHY IT NEEDS A POLICY

Why tentatively-accept-event needs a policy

This tool modifies calendar event status (acceptance state) in a user's Outlook calendar, which is a reversible write operation. The user can later change their acceptance status (accept fully, decline, or propose a new time). While it affects calendar data, the change is not destructive and can be undone, placing it in the Write category.

From the tool's definition Tool name 'tentatively-accept-event' and description 'Tentatively accepts a calendar event invitation' indicate 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 Assistant, 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 Assistant 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 Assistant 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 Assistant. 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 Assistant MCP server (titanzero/outlook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.