Skip to main content
Glama

github_code_security_get_configurations_for_enterprise

Retrieve code security configurations for a GitHub enterprise to review and manage security settings across organizations.

Instructions

Get code security configurations for an enterprise

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enterpriseYesenterprise
per_pageNoThe number of results per page (max 100). For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."
beforeNoA cursor, as given in the [Link header](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api#using-link-headers). If specified, the query only searches for results before this cursor. For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."
afterNoA cursor, as given in the [Link header](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api#using-link-headers). If specified, the query only searches for results after this cursor. For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."

Implementation Reference

  • The handler function for the 'github_code_security_get_configurations_for_enterprise' tool. Makes a GET request to `/enterprises/${args.enterprise}/code-security/configurations` with optional pagination parameters (per_page, before, after).
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/enterprises/${args.enterprise}/code-security/configurations`, undefined, { per_page: args.per_page, before: args.before, after: args.after });
    },
  • The input schema for the tool, validating parameters: enterprise (string), per_page (optional number), before (optional string), after (optional string).
    inputSchema: z.object({
      enterprise: z.string().describe("enterprise"),
      per_page: z.number().optional().describe("The number of results per page (max 100). For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\""),
      before: z.string().optional().describe("A cursor, as given in the [Link header](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api#using-link-headers). If specified, the query only searches for results before this cursor. For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\""),
      after: z.string().optional().describe("A cursor, as given in the [Link header](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api#using-link-headers). If specified, the query only searches for results after this cursor. For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\"")
    }),
  • The tool is defined as an entry in the codeSecurityTools array (line 5-18), which is exported and imported by src/index.ts (line 14) into the allToolModules array (line 65), then registered with server.tool() in a loop (lines 110-129).
    {
      name: "github_code_security_get_configurations_for_enterprise",
      description: "Get code security configurations for an enterprise",
      inputSchema: z.object({
        enterprise: z.string().describe("enterprise"),
        per_page: z.number().optional().describe("The number of results per page (max 100). For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\""),
        before: z.string().optional().describe("A cursor, as given in the [Link header](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api#using-link-headers). If specified, the query only searches for results before this cursor. For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\""),
        after: z.string().optional().describe("A cursor, as given in the [Link header](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api#using-link-headers). If specified, the query only searches for results after this cursor. For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\"")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("GET", `/enterprises/${args.enterprise}/code-security/configurations`, undefined, { per_page: args.per_page, before: args.before, after: args.after });
      },
    },
  • src/index.ts:55-65 (registration)
    The tool module is included in the allToolModules array under category 'code-security', enabling conditional loading via GITHUB_MCP_CATEGORIES env var.
    const allToolModules = [
      { category: "actions", tools: actionsTools },
      { category: "activity", tools: activityTools },
      { category: "agent-tasks", tools: agentTasksTools },
      { category: "apps", tools: appsTools },
      { category: "billing", tools: billingTools },
      { category: "campaigns", tools: campaignsTools },
      { category: "checks", tools: checksTools },
      { category: "classroom", tools: classroomTools },
      { category: "code-scanning", tools: codeScanningTools },
      { category: "code-security", tools: codeSecurityTools },
  • The githubRequest helper function that handles HTTP requests to the GitHub REST API, used by the tool's handler to execute the GET request.
    export async function githubRequest<T>(
      method: string,
      path: string,
      body?: Record<string, unknown>,
      params?: Record<string, string | number | boolean | string[] | undefined>
    ): Promise<T> {
      const url = new URL(`${BASE_URL}${path}`);
    
      if (params) {
        for (const [key, value] of Object.entries(params)) {
          if (value === undefined || value === null || value === "") continue;
          if (Array.isArray(value)) {
            url.searchParams.set(key, value.join(","));
          } else {
            url.searchParams.set(key, String(value));
          }
        }
      }
    
      const headers: Record<string, string> = {
        Authorization: `Bearer ${getToken()}`,
        Accept: "application/vnd.github+json",
        "X-GitHub-Api-Version": "2022-11-28",
        "User-Agent": "github-mcp/1.0.0",
      };
    
      if (body) {
        headers["Content-Type"] = "application/json";
      }
    
      const res = await fetch(url.toString(), {
        method,
        headers,
        body: body ? JSON.stringify(body) : undefined,
      });
    
      if (!res.ok) {
        const text = await res.text().catch(() => "");
        let detail = text;
        try {
          const json = JSON.parse(text);
          detail = json.message || text;
          if (json.errors) detail += ` -- ${JSON.stringify(json.errors)}`;
        } catch {}
        throw new Error(`GitHub API error ${res.status}: ${detail}`);
      }
    
      if (res.status === 204) return {} as T;
    
      return res.json() as Promise<T>;
    }
Behavior2/5

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

No annotations are present, so the description must carry the burden of behavioral disclosure. It does not mention that this is a read-only operation, any authentication needs, rate limits, or pagination behavior. The schema includes pagination params, but the description fails to clarify that results are paginated.

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

Conciseness3/5

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

The description is a single sentence, which is concise but lacks structure. It does not include a note about pagination or result format. Given the complexity, it is adequately short but not optimally informative.

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?

The description is incomplete for a list endpoint with pagination. No output schema is provided, so the description should clarify the return type (array of configurations) and pagination behavior. It fails to provide this essential context, leaving the agent to infer from the input schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema. It does not explain the purpose of 'before' and 'after' cursors or how they interact with pagination.

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 resource 'code security configurations' for an enterprise, distinguishing it from organization-level tools. However, it does not explicitly mention that it returns a list or that it supports pagination, which could be inferred from schema but lacks clarity for differentiation from single-configuration endpoints.

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 provided on when to use this tool versus alternatives like get_single_configuration_for_enterprise or get_default_configurations_for_enterprise. The description is a bare statement without context on selection or exclusion criteria.

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/Eyalm321/github-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server