Skip to main content
Glama
DynamicEndpoints

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

enforce_granular_roles

Enforce granular role assignments to replace Global Administrator privileges, implementing Microsoft 365 security policy MS.AAD.7.2v1 for compliance with CSA BOD 25-01 requirements.

Instructions

Enforce use of granular roles instead of Global Administrator (MS.AAD.7.2v1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'enforce_granular_roles' tool. It patches the roleManagementPolicies endpoint in Microsoft Graph API to set enforceGranularRoles to true and blockGlobalAdminForGeneralUse to true, then returns a success message.
    private async enforceGranularRoles() {
      try {
        // Configure role settings using Microsoft Graph API
        await this.graphClient
          .api('/policies/roleManagementPolicies')
          .patch({
            enforceGranularRoles: true,
            blockGlobalAdminForGeneralUse: true,
          });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Granular role usage enforced successfully',
            },
          ],
        };
      } catch (error: unknown) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to enforce granular roles: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • Registration of the 'enforce_granular_roles' tool in the ListTools response, including its name, description, and input schema (empty object).
    {
      name: 'enforce_granular_roles',
      description: 'Enforce use of granular roles instead of Global Administrator (MS.AAD.7.2v1)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema for the 'enforce_granular_roles' tool, which expects an empty object (no parameters).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • Dispatcher switch case in the CallToolRequest handler that routes calls to the enforceGranularRoles method.
    case 'enforce_granular_roles':
      return await this.enforceGranularRoles();
  • Helper code in getPolicyStatus that checks the enforcement status of granular roles from roleManagement policies.
    granularRoles: {
      enforced: roleManagement.enforceGranularRoles,
      compliant: true,
    },
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 implies a mutation action ('Enforce') but does not detail what enforcement entails (e.g., policy changes, user impacts, reversibility), permissions required, or any side effects like rate limits. This lack of operational context is a significant gap for a tool with potential security implications.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and includes a compliance reference for added context, making it highly concise and well-structured.

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 tool's complexity (implied security enforcement), lack of annotations, and no output schema, the description is incomplete. It does not explain what happens upon execution, expected outcomes, or error conditions, leaving critical behavioral aspects undocumented for an agent to use it effectively.

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 zero parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing on the tool's purpose instead, which aligns with the baseline for parameterless tools.

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 use of') and target resource ('granular roles instead of Global Administrator'), with a specific reference to a compliance standard ('MS.AAD.7.2v1'). However, it does not explicitly differentiate from sibling tools like 'configure_global_admins' or 'configure_role_alerts', which might involve related role management, keeping it from a perfect 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, such as other sibling tools for role configuration or admin management. It mentions a compliance standard but does not specify prerequisites, exclusions, or contextual triggers for enforcement, leaving usage ambiguous.

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