Lokka (Microsoft 365 MCP server)

4 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated:

3 can modify or destroy data
1 read-only
4 tools total

Community server · catalogue entry verified 11/06/2026

How to control Lokka (Microsoft 365 MCP server) ↓

What Lokka (Microsoft 365 MCP server) exposes to your agents

Read (1) Write / Execute (3) Destructive / Financial (0)
High Risk

The most dangerous Lokka (Microsoft 365 MCP server) tools

3 of Lokka (Microsoft 365 MCP server)'s 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Lokka (Microsoft 365 MCP server)

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

Rate limit write operations
{
  "add-graph-permission": {
    "limits": [
      {
        "counter": "add-graph-permission_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get-auth-status": {
    "limits": [
      {
        "counter": "get-auth-status_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 Lokka (Microsoft 365 MCP server) — 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.

All 4 Lokka (Microsoft 365 MCP server) tools

Questions about Lokka (Microsoft 365 MCP server)

How do I prevent bulk modifications through Lokka (Microsoft 365 MCP server)? +

The Lokka (Microsoft 365 MCP server) server has 3 write tools including add-graph-permission, Lokka-Microsoft, set-access-token. 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 Lokka (Microsoft 365 MCP server).

How many tools does the Lokka (Microsoft 365 MCP server) MCP server expose? +

4 tools across 2 categories: Read, Write. 1 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Lokka (Microsoft 365 MCP server)? +

Register the Lokka (Microsoft 365 MCP server) 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 Lokka (Microsoft 365 MCP server) tool call.

Deterministic rules across all 4 Lokka (Microsoft 365 MCP server) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4 Lokka (Microsoft 365 MCP server) 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.