View and manage authentication strength policies that define which authentication methods satisfy MFA requirements in Conditional Access.
AI agents use manage_authentication_strengths 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.
This tool modifies security policies that govern multi-factor authentication enforcement across Microsoft 365. While it includes read capabilities ('View'), the 'manage' operation allows creation/modification of authentication policies that directly impact organizational security posture. Misuse could weaken MFA requirements, disable strong authentication methods, or allow bypass of security controls.
From the tool's definition 'manage' indicates modification capability; 'authentication strength policies' are security-critical configurations that define MFA requirements in Conditional Access; the description explicitly states the tool both 'View and manage' these policies
Attacks that exploit this kind of access
View and manage authentication strength policies that define which authentication methods satisfy MFA requirements in Conditional Access. 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.
Register the Microsoft 365 Core MCP Server MCP server in PolicyLayer and add a rule for manage_authentication_strengths: 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.
manage_authentication_strengths is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_authentication_strengths 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.
Set action: deny in the PolicyLayer policy for manage_authentication_strengths. 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.
manage_authentication_strengths 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.
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 →