manage_identity_protection

WHAT IT DOES

What manage_identity_protection does on Microsoft 365 Core MCP Server

AI agents use manage_identity_protection to create or update resources in Microsoft 365 Core MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Microsoft 365 Core MCP Server environment.

WHY IT NEEDS A POLICY

Why manage_identity_protection needs a policy

The tool combines read capabilities (monitor risk detections, risky users) with write/remediation capabilities (risk remediation actions). 'Manage' implies the ability to dismiss risks, confirm compromised users, or unblock users — all of which modify Azure AD Identity Protection state.

From the tool's definition 'manage' and 'risk remediation actions' indicate the tool can modify identity protection state, not just read it

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_identity_protection Rate-limited

manage_identity_protection 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": {
    "manage_identity_protection": {
      "limits": [
        {
          "counter": "manage_identity_protection_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 Microsoft 365 Core MCP Server, so you can run agents against it safely.

FAQ

Questions about manage_identity_protection

What does the manage_identity_protection tool do? +

Monitor and manage Azure AD Identity Protection including risk detections, risky users, and risk remediation actions. It is categorised as a Write tool in the Microsoft 365 Core 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 manage_identity_protection? +

Register the Microsoft 365 Core MCP Server MCP server in PolicyLayer and add a rule for manage_identity_protection: 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 Microsoft 365 Core MCP Server. Nothing to install.

What risk level is manage_identity_protection? +

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

Can I rate-limit manage_identity_protection? +

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

Set action: deny in the PolicyLayer policy for manage_identity_protection. 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 manage_identity_protection? +

manage_identity_protection is provided by the Microsoft 365 Core MCP Server MCP server (roycedamien/m365-core-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.