Skip to main content
Glama
DynamicEndpoints

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

enforce_pam

Enforce Privileged Access Management to control privileged role assignments in Microsoft 365 environments, implementing CSA BOD 25-01 security requirements.

Instructions

Enforce PAM system for privileged role assignments (MS.AAD.7.5v1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that implements the 'enforce_pam' tool logic by configuring Privileged Access Management (PAM) settings via Microsoft Graph API.
    private async enforcePAM() {
      try {
        // Configure PAM settings using Microsoft Graph API
        await this.graphClient
          .api('/policies/privilegedAccessPolicy')
          .patch({
            requirePAMForPrivilegedRoles: true,
            blockDirectAssignment: true,
          });
    
        return {
          content: [
            {
              type: 'text',
              text: 'PAM system enforcement configured successfully',
            },
          ],
        };
      } catch (error: unknown) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to enforce PAM: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • Registration of the 'enforce_pam' tool in the list of available tools, including its description and empty input schema.
    {
      name: 'enforce_pam',
      description: 'Enforce PAM system for privileged role assignments (MS.AAD.7.5v1)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Dispatch case in the CallToolRequest handler that routes calls to the 'enforce_pam' tool to its implementation method.
    case 'enforce_pam':
      return await this.enforcePAM();
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 specify permissions required, potential side effects, or response behavior. This leaves critical operational details unclear for a tool that likely modifies system settings.

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 with no wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for a tool with no parameters.

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

Completeness3/5

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

Given the tool has no parameters and no output schema, the description is minimally adequate but lacks depth. It does not explain what 'enforce' entails operationally or what the expected outcome is, which is a gap for a mutation tool with no annotations to clarify behavior.

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 the schema description coverage is 100%, so no parameter documentation is needed. The description does not add parameter details, which is appropriate, but it includes a version reference ('MS.AAD.7.5v1') that provides some contextual semantics, slightly enhancing understanding beyond the schema.

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 the resource ('PAM system for privileged role assignments'), making the purpose specific and understandable. However, it does not differentiate this tool from sibling tools like 'enforce_granular_roles' or 'enforce_privileged_mfa', which also involve enforcement in similar domains, leaving some ambiguity in scope.

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 enforcement tools in the sibling list. It lacks context about prerequisites, timing, or exclusions, offering only a basic functional statement without operational 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