Skip to main content
Glama
DynamicEndpoints

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

block_legacy_auth

Disable outdated authentication methods to enhance security by preventing unauthorized access through weak protocols.

Instructions

Block legacy authentication (MS.AAD.1.1v1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic: patches the authenticationMethodsPolicy via Microsoft Graph API to block legacy authentication methods.
    private async blockLegacyAuth() { try { // Configure authentication policy using Microsoft Graph API await this.graphClient .api('/policies/authenticationMethodsPolicy') .patch({ allowLegacyAuthentication: false, blockLegacyAuthenticationMethods: true, }); return { content: [ { type: 'text', text: 'Legacy authentication blocked successfully', }, ], }; } catch (error: unknown) { throw new McpError( ErrorCode.InternalError, `Failed to block legacy authentication: ${error instanceof Error ? error.message : 'Unknown error'}` ); } }
  • Registers the tool in the ListTools response, including name, description, and input schema (empty object).
    { name: 'block_legacy_auth', description: 'Block legacy authentication (MS.AAD.1.1v1)', inputSchema: { type: 'object', properties: {}, }, },
  • Dispatches tool calls to the handler in the CallToolRequest switch statement.
    case 'block_legacy_auth': return await this.blockLegacyAuth();
  • Defines the input schema for the tool (empty object, no parameters required).
    inputSchema: { type: 'object', properties: {}, },

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