Skip to main content
Glama
DynamicEndpoints

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

get_policy_status

Check current compliance status of CISA M365 security policies to verify adherence to BOD 25-01 requirements for Microsoft 365 cloud services.

Instructions

Get current status of all CISA M365 security policies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for get_policy_status in Power Platform server that returns a mock status of security policies (TODO: real implementation).
    private async getPolicyStatus() {
      // TODO: Implement policy status check logic
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              environmentCreation: 'Restricted to admins',
              dlpPolicy: 'Configured',
              tenantIsolation: 'Enabled',
            }, null, 2),
          },
        ],
      };
    }
  • Handler for get_policy_status in Exchange Online server that queries Microsoft Graph API for various Exchange policy statuses and returns them in JSON.
    private async getPolicyStatus() {
      try {
        if (!this.graphClient) {
          throw new Error('Graph client not initialized');
        }
    
        const results = {
          policies: EXO_POLICIES,
          currentStatus: {
            externalForwarding: await this.graphClient.api('/admin/exchangeSettings/externalForwarding').get(),
            spfPolicies: await this.graphClient.api('/admin/domains/spfRecords').get(),
            dmarcPolicies: await this.graphClient.api('/admin/domains/dmarcRecords').get(),
            smtpAuth: await this.graphClient.api('/admin/exchangeSettings/smtpAuth').get(),
            sharingPolicies: await this.graphClient.api('/admin/exchangeSettings/sharingPolicies').get(),
            externalSenderWarning: await this.graphClient.api('/admin/exchangeSettings/externalSenderWarning').get(),
            mailboxAudit: await this.graphClient.api('/admin/exchangeSettings/mailboxAudit').get()
          }
        };
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(results, null, 2)
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error occurred';
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get policy status: ${errorMessage}`
        );
      }
    }
  • Handler for get_policy_status in Defender server that fetches current Defender policy statuses via Microsoft Graph API.
    private async getPolicyStatus() {
      try {
        if (!this.graphClient) {
          throw new Error('Graph client not initialized');
        }
    
        const results = {
          policies: DEFENDER_POLICIES,
          currentStatus: {
            securityPolicies: await this.graphClient.api('/security/securityPresetPolicies').get(),
            piiProtection: await this.graphClient.api('/security/sensitiveTypes').get(),
            auditConfig: await this.graphClient.api('/security/auditLogs/config').get()
          }
        };
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(results, null, 2)
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error occurred';
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get policy status: ${errorMessage}`
        );
      }
    }
  • Handler for get_policy_status in Teams server that queries multiple Teams policies via Graph API and computes their compliance status.
    private async getPolicyStatus() {
      try {
        // Get current settings using Microsoft Graph API
        const [
          meetingPolicy,
          federationSettings,
          externalUserSettings,
          emailSettings,
        ] = await Promise.all([
          this.graphClient.api('/policies/teamsAppSetupPolicies/global').get(),
          this.graphClient.api('/policies/teamsFederationSettings').get(),
          this.graphClient.api('/policies/teamsExternalUserSettings').get(),
          this.graphClient.api('/policies/teamsEmailSettings').get(),
        ]);
    
        const status = {
          anonymousMeetings: {
            disabled: !meetingPolicy.allowAnonymousUsersToStartMeeting,
            compliant: !meetingPolicy.allowAnonymousUsersToStartMeeting,
          },
          externalAccess: {
            allowedDomains: federationSettings.allowedDomains,
            compliant: federationSettings.allowedDomains.length > 0 &&
                      !federationSettings.allowTeamsConsumer,
          },
          unmanagedUsers: {
            disabled: !externalUserSettings.allowUnmanagedUsersToStartChat,
            compliant: !externalUserSettings.allowUnmanagedUsersToStartChat,
          },
          skypeUsers: {
            blocked: !federationSettings.allowSkypeUsers,
            compliant: !federationSettings.allowSkypeUsers,
          },
          emailIntegration: {
            disabled: !emailSettings.allowEmailIntegration,
            compliant: !emailSettings.allowEmailIntegration,
          },
        };
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(status, null, 2),
            },
          ],
        };
      } catch (error: unknown) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get policy status: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
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 read-only operation ('Get'), but doesn't specify if it requires authentication, has rate limits, returns real-time or cached data, or details the output format. This is a significant gap for a tool with zero annotation coverage.

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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the status output includes (e.g., policy names, compliance levels, timestamps) or behavioral aspects like error handling, leaving the agent with insufficient context for effective use.

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 schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for this scenario is 4, as the description appropriately focuses on the tool's purpose without redundant parameter information.

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 verb 'Get' and the resource 'current status of all CISA M365 security policies', making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its siblings (e.g., configuration or enforcement tools), which prevents 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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, timing, or comparisons with sibling tools, 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