Skip to main content
Glama
rajbos

GHAS MCP server (GitHub Advanced Security)

list_secret_scanning_alerts

Retrieve and display GitHub Advanced Security secret scanning alerts for a specified repository to identify and manage potential security risks.

Instructions

List the current GitHub Advanced Security secret scanning alerts for a repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYes
repoYes

Implementation Reference

  • src/index.ts:56-63 (registration)
    Registration of the 'list_secret_scanning_alerts' tool in the ListTools response, including name, description, and input schema definition.
    {
        name: "list_secret_scanning_alerts",
        description: "List the current GitHub Advanced Security secret scanning alerts for a repository",
        inputSchema: zodToJsonSchema(z.object({
            owner: z.string(),
            repo: z.string(),
        })),
    },
  • The handler in the CallToolRequestSchema that parses arguments, calls the implementation function, and formats the response for the 'list_secret_scanning_alerts' tool.
    case "list_secret_scanning_alerts": {
        const args = z.object({ owner: z.string(), repo: z.string() }).parse(request.params.arguments);
        const alerts = await listSecretScanningAlerts(args.owner, args.repo);
        return {
            content: [{ type: "text", text: JSON.stringify(alerts, null, 2) }],
        };
    }
  • The core implementation function that validates access, uses Octokit to fetch secret scanning alerts from GitHub API, and returns the data.
    export async function listSecretScanningAlerts(owner: string, repo: string) {
        const octokit = await validateAccessToken(owner, repo);
    
        console.log(`Fetching secret scanning alerts for repository: [${owner}/${repo}]`);
        console.log("Starting to fetch secret scanning alerts...");
        try {
            const { data } = await octokit.rest.secretScanning.listAlertsForRepo({
                owner,
                repo
            });
            console.log(`Fetched [${data.length}] secret scanning alerts.`);
            return data;
        } catch (error) {
            console.error("Error fetching secret scanning alerts:", error);
            throw 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 states the tool lists alerts but does not describe key traits like whether it requires authentication, has rate limits, returns paginated results, or what the output format is. This leaves significant gaps in understanding how the tool behaves.

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 that efficiently conveys the core purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 (listing security alerts), lack of annotations, no output schema, and low parameter schema coverage, the description is incomplete. It does not provide enough context on behavior, output, or parameter usage, making it inadequate for effective tool invocation.

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

Parameters2/5

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

The input schema has 2 parameters with 0% description coverage, so the schema provides no semantic information. The description does not add any meaning to the parameters (owner, repo), such as explaining what they represent or how to format them, failing to compensate for the low schema coverage.

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 ('List') and the resource ('GitHub Advanced Security secret scanning alerts for a repository'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'list_code_scanning_alerts' or 'list_dependabot_alerts', which would be needed for a score of 5.

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 the sibling tools listed. It mentions the context ('for a repository') but lacks explicit when/when-not instructions or comparisons to other alert-listing tools, leaving usage unclear.

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

Related 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/rajbos/ghas-mcp-server'

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