Skip to main content
Glama
DynamicEndpoints

BOD-25-01-CSA-Microsoft-Policy-MCP

enforce_phishing_resistant_mfa

Enforce phishing-resistant multi-factor authentication for all users to meet BOD 25-01 compliance requirements in Microsoft 365 environments.

Instructions

Enforce phishing-resistant MFA for all users (MS.AAD.3.1v1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic: patches the Microsoft Graph API /policies/authenticationMethodsPolicy to enable phishing-resistant MFA methods (FIDO2 and Windows Hello for Business).
    private async enforcePhishingResistantMFA() {
      try {
        // Configure MFA policy using Microsoft Graph API
        await this.graphClient
          .api('/policies/authenticationMethodsPolicy')
          .patch({
            policies: {
              fido2: {
                isEnabled: true,
                isSelfServiceRegistrationAllowed: true,
              },
              windowsHelloForBusiness: {
                isEnabled: true,
                isSelfServiceRegistrationAllowed: true,
              },
            },
          });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Phishing-resistant MFA enforced successfully',
            },
          ],
        };
      } catch (error: unknown) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to enforce phishing-resistant MFA: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • Tool registration in the ListTools response, including name, description, and input schema (empty object).
    {
      name: 'enforce_phishing_resistant_mfa',
      description: 'Enforce phishing-resistant MFA for all users (MS.AAD.3.1v1)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Dispatcher case in the CallToolRequest handler that routes to the enforcePhishingResistantMFA method.
    case 'enforce_phishing_resistant_mfa':
      return await this.enforcePhishingResistantMFA();
  • Input schema definition for the tool (empty object, no parameters).
    inputSchema: {
      type: 'object',
      properties: {},
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Enforce' implies a configuration change or policy application, but the description doesn't specify whether this requires admin privileges, what happens to existing MFA settings, whether it's reversible, or what the expected outcome looks like. For a zero-parameter mutation tool with no annotation coverage, this represents significant gaps in behavioral transparency.

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

Conciseness3/5

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

The description is extremely concise (one sentence) but the parenthetical reference 'MS.AAD.3.1v1' adds noise without clear value to an AI agent. While brief, it's not optimally structured - the compliance reference should either be explained or omitted for better front-loading of actionable information.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'enforce' entails operationally, what success/failure looks like, or any side effects. The MS.AAD.3.1v1 reference doesn't compensate for these gaps. Given the tool's likely administrative nature and impact on user authentication, more context is needed.

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?

With zero parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema coverage is complete. No additional parameter information is needed or provided.

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 the action ('Enforce') and target ('phishing-resistant MFA for all users'), providing a specific verb+resource combination. It distinguishes from some siblings like 'enforce_alternative_mfa' and 'enforce_privileged_mfa' by specifying the phishing-resistant aspect and universal scope. However, it doesn't fully differentiate from all possible similar tools in the broader context.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'enforce_alternative_mfa' or 'enforce_privileged_mfa'. There's no mention of prerequisites, timing considerations, or exclusion criteria. The MS.AAD.3.1v1 reference might imply a compliance context but doesn't offer practical usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DynamicEndpoints/Automated-BOD-25-01-CISA-Microsoft-Policies-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server