Skip to main content
Glama
DynamicEndpoints

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

restrict_app_registration

Enforce administrator-only application registration to prevent unauthorized access and maintain security compliance in Microsoft 365 environments.

Instructions

Allow only administrators to register applications (MS.AAD.5.1v1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that executes the tool logic by patching the Microsoft Graph API to restrict app registrations to administrators only.
    private async restrictAppRegistration() {
      try {
        // Configure app registration settings using Microsoft Graph API
        await this.graphClient
          .api('/policies/applicationRegistrationManagement')
          .patch({
            restrictAppRegistration: true,
            restrictNonAdminUsers: true,
          });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Application registration restricted to administrators successfully',
            },
          ],
        };
      } catch (error: unknown) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to restrict app registration: ${error instanceof Error ? error.message : 'Unknown error'}`
        );
      }
    }
  • The switch case in the CallToolRequest handler that dispatches to the restrictAppRegistration method.
    case 'restrict_app_registration':
      return await this.restrictAppRegistration();
  • The tool definition including name, description, and input schema (empty object) registered in the ListTools response.
    {
      name: 'restrict_app_registration',
      description: 'Allow only administrators to register applications (MS.AAD.5.1v1)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Helper logic in getPolicyStatus that checks the status of app registration restrictions.
    appRegistration: {
      restrictedToAdmins: appRegistration.restrictAppRegistration && 
                        appRegistration.restrictNonAdminUsers,
      compliant: true,
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool enforces a restriction policy but doesn't describe what happens when invoked: whether it's a one-time configuration change, requires admin permissions, has side effects on existing applications, or provides confirmation. For a policy enforcement tool with zero annotation coverage, this leaves critical behavioral aspects unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core purpose without unnecessary words. The MS.AAD.5.1v1 reference adds context but doesn't disrupt conciseness. It could be slightly improved by integrating the reference more naturally, but it's well-structured and front-loaded.

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's complexity (policy enforcement), lack of annotations, and no output schema, the description is minimally adequate. It states what the tool does but lacks details on behavioral impact, permissions needed, or result format. For a security configuration tool, this leaves gaps that could lead to misuse or uncertainty about outcomes.

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% (empty schema is fully described). The description doesn't need to explain parameters, and the baseline for zero parameters is 4. The MS.AAD.5.1v1 reference might hint at a compliance standard but doesn't relate to parameters.

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: 'Allow only administrators to register applications' specifies the action (allow) and resource (application registration) with a clear restriction (administrators only). It distinguishes from siblings like 'restrict_app_consent' by focusing on registration rather than consent, though it doesn't explicitly compare them. The MS.AAD.5.1v1 reference adds specificity but doesn't fully explain the distinction.

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. It doesn't mention prerequisites, timing considerations, or compare it to sibling tools like 'restrict_app_consent' or 'configure_admin_consent'. The agent must infer usage from the purpose alone, which is insufficient for informed tool selection.

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