Skip to main content
Glama
DynamicEndpoints

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

disable_password_expiry

Disable password expiration policies to maintain consistent access without periodic password changes, addressing MS.AAD.6.1v1 compliance requirements.

Instructions

Disable password expiration (MS.AAD.6.1v1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'disable_password_expiry' tool. It uses the Microsoft Graph API to patch the password policy, setting passwords to never expire.
    private async disablePasswordExpiry() {
      try {
        // Configure password policy using Microsoft Graph API
        await this.graphClient
          .api('/policies/passwordPolicy')
          .patch({
            passwordExpirationPolicy: {
              passwordExpirationDays: 0,
              neverExpire: true,
            },
          });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Password expiration disabled successfully',
            },
          ],
        };
      } catch (error: unknown) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to disable password expiry: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • The switch case in the CallToolRequest handler that routes calls to the disablePasswordExpiry method.
    case 'disable_password_expiry':
      return await this.disablePasswordExpiry();
  • Registers the tool in the ListTools response, including name, description, and input schema (empty object).
    {
      name: 'disable_password_expiry',
      description: 'Disable password expiration (MS.AAD.6.1v1)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Defines the input schema for the tool as an empty object (no parameters required).
    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 the full burden of behavioral disclosure. It states the action ('Disable') but doesn't clarify if this is a permanent change, requires specific authentication, has side effects (e.g., on security policies), or what the expected outcome is. This leaves significant gaps in understanding the tool's behavior beyond its basic purpose.

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 extremely concise—a single phrase that directly states the tool's function without any unnecessary words. It is front-loaded and wastes no space, making it efficient for quick comprehension by an AI agent.

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?

Given the complexity of a security configuration tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after disabling password expiry (e.g., confirmation message, error handling) or any dependencies. For a tool that likely involves system changes, more context is needed to ensure safe and correct usage.

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?

The tool has 0 parameters, and the input schema has 100% description coverage, so there are no parameters to document. The description doesn't need to add parameter semantics, but it could have mentioned if any implicit inputs (like user context) are required. Since there are no parameters, a baseline of 4 is appropriate, as it avoids misleading or missing param info.

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 tool's purpose with a specific verb ('Disable') and resource ('password expiration'), making it immediately understandable. However, it doesn't distinguish this tool from its siblings (like 'configure_admin_alerts' or 'enforce_phishing_resistant_mfa'), which are also security configuration tools but for different aspects, so it doesn't reach the highest score.

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 or in what context it should be applied. It lacks any mention of prerequisites, such as administrative permissions or specific scenarios where disabling password expiry is appropriate, leaving the agent without usage direction.

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