Skip to main content
Glama

github_code_security_update_enterprise_configuration

Update an enterprise's custom code security configuration to align with security policies.

Instructions

Update a custom code security configuration for an enterprise

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enterpriseYesenterprise
configuration_idYesconfiguration_id
bodyNoRequest body (JSON object)

Implementation Reference

  • The handler function for the tool 'github_code_security_update_enterprise_configuration' that executes the core logic: sends a PATCH request to `/enterprises/{enterprise}/code-security/configurations/{configuration_id}` with the request body.
    handler: async (args: Record<string, any>) => {
      return githubRequest("PATCH", `/enterprises/${args.enterprise}/code-security/configurations/${args.configuration_id}`, args.body, undefined);
    },
  • The input schema for the tool, specifying three parameters: enterprise (string), configuration_id (string), and an optional body (record/JSON object).
    inputSchema: z.object({
      enterprise: z.string().describe("enterprise"),
      configuration_id: z.string().describe("configuration_id"),
      body: z.record(z.string(), z.unknown()).optional().describe("Request body (JSON object)")
    }),
  • src/index.ts:110-129 (registration)
    Where tools are registered with the MCP server via server.tool() - iterates over all tool modules including codeSecurityTools which contains the target tool.
    for (const tool of allTools) {
      server.tool(
        tool.name,
        tool.description,
        tool.inputSchema.shape as any,
        async (args: any) => {
          try {
            const result = await tool.handler(args as any);
            return {
              content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
            };
          } catch (err) {
            const message = err instanceof Error ? err.message : String(err);
            return {
              content: [{ type: "text" as const, text: `Error: ${message}` }],
              isError: true,
            };
          }
        }
      );
  • src/index.ts:65-65 (registration)
    The import and registration of codeSecurityTools array (which contains this tool) into the allToolModules array.
    { category: "code-security", tools: codeSecurityTools },
  • The githubRequest helper function used by the handler to make HTTP requests to the GitHub API.
    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?

With no annotations, the description should disclose behavioral traits but does not. It omits details like whether updates are partial or full replacements, permission requirements, reversibility, or side effects. The description only states the basic purpose.

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, clear sentence that is front-loaded and easy to parse. It is concise but slightly overly minimal; adding one or two additional details would not harm conciseness.

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 (enterprise scope, nested body object, no output schema), the description is insufficient. It does not explain what the body should contain, what the response is, or how it differs from related tools. The description leaves significant gaps for an agent to understand correct usage.

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 coverage is 100%, so the baseline is 3. However, the description adds no meaning beyond the schema parameter names and types. The body parameter is described merely as 'Request body (JSON object)' without specifying permissible properties, which is minimally informative.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (Update), the resource (custom code security configuration), and the scope (for an enterprise). This differentiates it from sibling tools like update_configuration (which operates at the organization level).

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 such as update_configuration or create_configuration_for_enterprise. The description lacks context on prerequisites, when updates are appropriate, or when other actions might be preferred.

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