Skip to content
actionlake
Start free

Connectors · Identity & security

Microsoft Entra ID Protection (Graph) MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Microsoft Entra ID Protection (Graph) and the rest of your systems. It gives your agent 15 Microsoft Entra ID Protection (Graph) actions (10 reads, 0 writes and 5 that wait for a confirmation) and holds the Microsoft Entra ID Protection (Graph) credential itself, so the agent never does. It paces Microsoft Entra ID Protection (Graph)'s limits and records every call.

Connect Microsoft Entra ID Protection (Graph) freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "m365_graph_identity_protection.risk_detections_list",  intent: "check which Microsoft Entra ID Protection (Graph) account is connected"}# List risk detections · read · 1 upstream call
  • 15actionsin one signed file
  • 10readlook, never change
  • 0writecreate and update
  • 5wait for a yesdestructive, confirmed first

Set up

Connect Microsoft Entra ID Protection (Graph) in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Microsoft Entra ID Protection (Graph).

    OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in. actionlake stores what you paste write-only, sealed under your tenant's key.

    • client_idEntra application (client) id
    • client_secretEntra client secret
    • tenant_idYour Microsoft Entra ID Protection (Graph) tenant id
    account { op: "connections.requirements", service: "m365_graph_identity_protection" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "m365_graph_identity_protection.risk_detections_list" }# list risk detections · read · 1 upstream callcheck { action: "m365_graph_identity_protection.risky_users_dismiss", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Microsoft Entra ID Protection (Graph) at a glance

Sign-in
OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in.
You provide
client_idclient_secret
Setup fields
tenant_id
Limits we pace to
10,000 calls per 10 minutes, per connection
API covered
Microsoft Entra ID Protection (Graph) API v1.0graph.microsoft.com/v1.0
Built from
Microsoft Entra ID Protection (Graph)'s documentation, read 23 October 2026learn.microsoft.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
10 of 10 reads, for up to an hour; a write clears what it affects
Shared entities
1, so ask can line Microsoft Entra ID Protection (Graph) up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Microsoft Entra ID Protection (Graph).

15 actions in 11 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 10readlook, never change
  • 0writecreate and update
  • 5destructivewait for a confirmation

  1. Risk detections

    2

    2 read · 0 write · 0 destructive

    List risk detections · Get risk detections

  2. Risky service principals

    2

    2 read · 0 write · 0 destructive

    List risky service principals · Get risky service principals

  3. Risky users

    2

    2 read · 0 write · 0 destructive

    List risky users · Get risky users

  4. Service principal risk detections

    2

    2 read · 0 write · 0 destructive

    List service principal risk detections · Get service principal risk detections

  5. Risky service principals confirm compromised

    1

    0 read · 0 write · 1 destructive

    Risky service principals confirm compromised

  6. Risky service principals dismiss

    1

    0 read · 0 write · 1 destructive

    Risky service principals dismiss

  7. Risky service principals history

    1

    1 read · 0 write · 0 destructive

    List risky service principals history

  8. Risky users confirm compromised

    1

    0 read · 0 write · 1 destructive

    Risky users confirm compromised

3 more areas · 3 actions
  • Risky users confirm safe 1
  • Risky users dismiss 1
  • Risky users history 1

Top actions

The Microsoft Entra ID Protection (Graph) API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 2 of Microsoft Entra ID Protection (Graph)'s 2 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
m365_graph_identity_protection.risk_detections_listList risk detectionsGet a list of the riskDetection objects and their properties.readidentity.risk_detection.list2 connectors
m365_graph_identity_protection.risk_detections_getGet risk detectionsRead the properties and relationships of a riskDetection object.readidentity.risk_detection.get3 connectors
m365_graph_identity_protection.risky_users_listList risky usersGet a list of the riskyUser objects and their properties.readthis connector
m365_graph_identity_protection.risky_service_principals_listList risky service principalsRetrieve the properties and relationships of riskyServicePrincipal objects.readthis connector
m365_graph_identity_protection.risky_users_dismissRisky users dismissDismiss the risk of one or more riskyUser objects. This action sets the targeted user's risk level to none.destructivethis connector
m365_graph_identity_protection.service_principal_risk_detections_listList service principal risk detectionsRetrieve the properties of a collection of servicePrincipalRiskDetection objects.readthis connector

Try it

Prompts to paste into Claude.

Each one names the Microsoft Entra ID Protection (Graph) actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Who has access in Microsoft Entra ID Protection (Graph)? List every user and their role.

    callsm365_graph_identity_protection.risky_users_list

Governance for Microsoft Entra ID Protection (Graph)

Destructive actions wait for a yes.

5 Microsoft Entra ID Protection (Graph) actions are destructive. These are all of them:

  • Risky users dismissm365_graph_identity_protection.risky_users_dismiss
  • Risky users confirm compromisedm365_graph_identity_protection.risky_users_confirm_compromised
  • Risky users confirm safem365_graph_identity_protection.risky_users_confirm_safe
  • Risky service principals dismissm365_graph_identity_protection.risky_service_principals_dismiss
  • Risky service principals confirm compromisedm365_graph_identity_protection.risky_service_principals_confirm_compromised

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dom365_graph_identity_protection.risky_users_dismissconfirm_policy: human

Risky users dismiss?

intent: the user asked me to risky users dismiss

run suspended · waiting for a named person · key m365-graph-identity-protection-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "m365-graph-identity-protection-agent",  allowed_actions: ["m365_graph_identity_protection.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "m365_graph_identity_protection.risky_users_dismiss", approver: "[email protected]" },    { match: "m365_graph_identity_protection.risky_users_confirm_compromised", approver: "[email protected]" },    { match: "m365_graph_identity_protection.risky_users_confirm_safe", approver: "[email protected]" }  ]}
Illustrative. Scoped to Microsoft Entra ID Protection (Graph) only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Microsoft Entra ID Protection (Graph) costs on actionlake.

Every Microsoft Entra ID Protection (Graph) action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Microsoft Entra ID Protection (Graph) refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 15 Microsoft Entra ID Protection (Graph) actions
  • 6actions pageeach page of a long list is one call
  • 10reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Microsoft Entra ID Protection (Graph) action.

15 actions by area: the id your agent calls, what it does, and its effect.

Risk detections2
  • m365_graph_identity_protection.risk_detections_getGet risk detectionsread
  • m365_graph_identity_protection.risk_detections_listList risk detectionsread
Risky service principals2
  • m365_graph_identity_protection.risky_service_principals_getGet risky service principalsread
  • m365_graph_identity_protection.risky_service_principals_listList risky service principalsread
Risky users2
  • m365_graph_identity_protection.risky_users_getGet risky usersread
  • m365_graph_identity_protection.risky_users_listList risky usersread
Service principal risk detections2
  • m365_graph_identity_protection.service_principal_risk_detections_getGet service principal risk detectionsread
  • m365_graph_identity_protection.service_principal_risk_detections_listList service principal risk detectionsread
Risky service principals confirm compromised1
  • m365_graph_identity_protection.risky_service_principals_confirm_compromisedRisky service principals confirm compromiseddestructive
Risky service principals dismiss1
  • m365_graph_identity_protection.risky_service_principals_dismissRisky service principals dismissdestructive
Risky service principals history1
  • m365_graph_identity_protection.risky_service_principals_history_listList risky service principals historyread
Risky users confirm compromised1
  • m365_graph_identity_protection.risky_users_confirm_compromisedRisky users confirm compromiseddestructive
Risky users confirm safe1
  • m365_graph_identity_protection.risky_users_confirm_safeRisky users confirm safedestructive
Risky users dismiss1
  • m365_graph_identity_protection.risky_users_dismissRisky users dismissdestructive
Risky users history1
  • m365_graph_identity_protection.risky_users_history_listList risky users historyread

Questions

The Microsoft Entra ID Protection (Graph) MCP server, answered.

Is there a Microsoft Entra ID Protection (Graph) MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 15 Microsoft Entra ID Protection (Graph) actions across risk detections, risky service principals, risky users and service principal risk detections, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Microsoft Entra ID Protection (Graph).

What do I need to connect Microsoft Entra ID Protection (Graph)?

Entra application (client) id and Entra client secret. Plus your tenant id. The free call account { op: "connections.requirements", service: "m365_graph_identity_protection" } lists exactly what to paste.

Can an AI agent delete or change things in Microsoft Entra ID Protection (Graph)?

Only if its key allows it, and only with an explicit confirmation. 5 Microsoft Entra ID Protection (Graph) actions are destructive, including risky users dismiss, risky users confirm compromised and risky users confirm safe. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Microsoft Entra ID Protection (Graph) API limit?

actionlake paces every call to the limits in the Microsoft Entra ID Protection (Graph) service file: 10,000 calls per 10 minutes per connection. Repeated reads are answered from cache (10 Microsoft Entra ID Protection (Graph) actions can be), which never reaches Microsoft Entra ID Protection (Graph).

What does a Microsoft Entra ID Protection (Graph) action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (6 Microsoft Entra ID Protection (Graph) actions page). Cache hits, searches, dry runs and calls Microsoft Entra ID Protection (Graph) refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Microsoft Entra ID Protection (Graph) API does it cover?

The Microsoft Entra ID Protection (Graph) API v1.0 at graph.microsoft.com/v1.0. It is built from Microsoft Entra ID Protection (Graph)'s documentation as read on 23 October 2026. 15 actions in 11 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Microsoft Entra ID Protection (Graph) data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Microsoft Entra ID Protection (Graph) credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Microsoft Entra ID Protection (Graph)

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Microsoft Entra ID Protection (Graph); the name is the vendor's own. Counts are from the Microsoft Entra ID Protection (Graph) service file, version 1.0.0.

Give your agent Microsoft Entra ID Protection (Graph) today.

Connect Microsoft Entra ID Protection (Graph) freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.