manage_azuread_devices

Manage Azure AD registered devices - enable, disable, delete, and monitor devices

Server Microsoft 365 Core MCP Server roycedamien/m365-core-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What manage_azuread_devices does on Microsoft 365 Core MCP Server

AI agents call manage_azuread_devices to permanently remove resources in Microsoft 365 Core MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why manage_azuread_devices needs a policy

The tool explicitly supports deleting Azure AD devices, which is an irreversible destructive action. Device deletion in Azure AD can disrupt user access and MDM enrollment. Even the enable/disable operations have significant blast radius for managed device fleets. Per the rules, the most severe applicable category applies — Destructive due to the delete capability.

From the tool's definition 'enable, disable, delete, and monitor devices' — the delete operation irreversibly removes Azure AD registered devices

Questions about manage_azuread_devices

What does the manage_azuread_devices tool do? +

Manage Azure AD registered devices - enable, disable, delete, and monitor devices. It is categorised as a Destructive tool in the Microsoft 365 Core MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on manage_azuread_devices? +

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

manage_azuread_devices is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit manage_azuread_devices? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.