manage_azure_ad_devices · Microsoft 365 Core MCP Server MCP

WHAT IT DOES

What manage_azure_ad_devices does on Microsoft 365 Core MCP Server

AI agents use manage_azure_ad_devices 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_azure_ad_devices needs a policy

This tool modifies Azure AD device configurations including compliance settings and BitLocker keys. 'Device actions' could include remote wipe or disable operations which approach Destructive, but the primary framing is management/configuration (Write). BitLocker key access is sensitive. High severity due to potential to alter compliance posture across enterprise devices or expose encryption keys.

From the tool's definition Manage devices registered in Azure AD including device compliance, BitLocker keys, and device actions

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_azure_ad_devices Rate-limited

manage_azure_ad_devices 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_azure_ad_devices": {
      "limits": [
        {
          "counter": "manage_azure_ad_devices_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_azure_ad_devices

What does the manage_azure_ad_devices tool do? +

Manage devices registered in Azure AD including device compliance, BitLocker keys, and device 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_azure_ad_devices? +

Register the Microsoft 365 Core MCP Server MCP server in PolicyLayer and add a rule for manage_azure_ad_devices: 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_azure_ad_devices? +

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

Can I rate-limit manage_azure_ad_devices? +

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

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

manage_azure_ad_devices 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.