M365

85 tools. 52 can modify or destroy data without limits.

9 destructive tools with no built-in limits. Policy required.

Last updated:

52 can modify or destroy data
33 read-only
85 tools total

Community server · catalogue entry verified 02/07/2026

How to control M365 ↓

What M365 exposes to your agents

Read (33) Write / Execute (43) Destructive / Financial (9)
Critical Risk

The most dangerous M365 tools

52 of M365's 85 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control M365

PolicyLayer is an MCP gateway — it sits between your AI agents and M365, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "calendar_delete_calendar": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "account_authenticate": {
    "limits": [
      {
        "counter": "account_authenticate_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "account_list": {
    "limits": [
      {
        "counter": "account_list_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register M365 — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON M365 →

Instant setup, no code required.

All 85 M365 tools

WRITE 43 tools
Write account_authenticate account_authenticate Write account_complete_auth account_complete_auth Write cache_invalidate cache_invalidate Write calendar_create_calendar calendar_create_calendar Write calendar_create_event calendar_create_event Write calendar_forward_event calendar_forward_event Write calendar_propose_new_time calendar_propose_new_time Write calendar_respond_event calendar_respond_event Write calendar_update_event calendar_update_event Write contact_add_to_list contact_add_to_list Write contact_create contact_create Write contact_create_list contact_create_list Write contact_update contact_update Write email_add_category email_add_category Write email_archive email_archive Write email_create_draft email_create_draft Write email_flag email_flag Write email_forward email_forward Write email_mark_read email_mark_read Write email_move email_move Write email_reply email_reply Write email_reply_all email_reply_all Write email_send email_send Write email_update email_update Write emailfolders_create emailfolders_create Write emailfolders_mark_all_as_read emailfolders_mark_all_as_read Write emailfolders_move emailfolders_move Write emailfolders_rename emailfolders_rename Write emailrules_create emailrules_create Write emailrules_move_bottom emailrules_move_bottom Write emailrules_move_down emailrules_move_down Write emailrules_move_top emailrules_move_top Write emailrules_move_up emailrules_move_up Write emailrules_update emailrules_update Write file_copy file_copy Write file_create file_create Write file_move file_move Write file_rename file_rename Write file_share file_share Write file_update file_update Write folder_create folder_create Write folder_move folder_move Write folder_rename folder_rename

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about M365

Can an AI agent delete data through the M365 MCP server? +

Yes. The M365 server exposes 9 destructive tools including calendar_delete_calendar, calendar_delete_event, contact_delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through M365? +

The M365 server has 43 write tools including account_authenticate, account_complete_auth, cache_invalidate. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach M365.

How many tools does the M365 MCP server expose? +

85 tools across 4 categories: Destructive, Execute, Read, Write. 33 are read-only. 52 can modify, create, or delete data.

How do I enforce a policy on M365? +

Register the M365 MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every M365 tool call.

Deterministic rules across all 85 M365 tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

85 M365 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.