IntuneRW-Core

Overview Schema Source Related Servers Discussions Admin

manage_identity_protection

Inspect and manage Entra ID identity protection: list auth methods and MFA status, review sign-in/audit logs, and dismiss or confirm risky users.

Instructions

Manage identity protection, authentication methods, sign-in logs and risky users.

action values: get_auth_methods — List authentication methods for a user (user_id) get_mfa_status — Check MFA registration status for a user (user_id) delete_auth_method — Remove an authentication method (user_id, method_id, confirm=True) get_auth_methods_policy — Get tenant-wide authentication methods policy get_sign_in_logs — Sign-in logs (filter_query for OData filter, top) get_directory_audit_logs — Directory audit logs (filter_query, top) get_risky_users — List risky users get_risk_detections — Get risk detection events dismiss_risky_user — Dismiss risk for a user (body: {userIds: [...]}) confirm_compromised — Confirm users as compromised (body: {userIds: [...]})

Input Schema

Name	Required	Description	Default
`top`	No
`body`	No
`action`	Yes
`user_id`	No
`method_id`	No
`filter_query`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 21, 2026

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full transparency burden. It provides useful action-specific details, such as confirm=True for delete_auth_method and the body structure for dismiss_risky_user/confirm_compromised, but it does not disclose potential side effects, required permissions, or irreversibility of mutation actions. This is a moderate level of transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is highly structured with a clear purpose line followed by a concise action list. Each line is short and includes the relevant parameters, avoiding redundancy. The format is easy to parse and front-loads the most critical information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex with 10 actions, but the description covers all actions and links parameters to each. Some actions like get_risk_detections only say 'Get risk detection events' without noting applicable parameters, but the output schema covers return values. Overall, the description is reasonably complete for the tool's size, though minor gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: it explains the action parameter values and shows how parameters like user_id, method_id, filter_query, and body are used per action. It does not define every parameter globally (e.g., top is only mentioned in log actions), but it adds substantial meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it manages identity protection, authentication methods, sign-in logs, and risky users. The action list gives concrete sub-operations, making the tool's scope unambiguous. However, 'manage' is a broad verb and it doesn't explicitly contrast with sibling tools like manage_entra_users or manage_conditional_access, so it doesn't fully capitalize on differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the action list: use this tool for identity protection tasks like auth methods, sign-in logs, and risky users. The description does not explicitly state when to choose this over sibling tools, nor does it mention exclusions. Given the lack of explicit alternatives, the guidance is adequate but not strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.