mcp-github-enterprise

List secret-scanning alerts

list_secret_scanning_alerts

Read-onlyIdempotent

List an organization's secret-scanning alerts by state to review type, repository, and location; matched secret values are excluded from results.

Instructions

List the organization's secret-scanning alerts (type, state, repo, location). The matched secret value itself is dropped and never returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "org": "<org>"
    },
    "name": "list_secret_scanning_alerts"
  }
}

Input Schema

Name	Required	Description	Default
`org`	Yes	Organization login (must be within GHE_ORG_ALLOWLIST when that is set)
`state`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 7, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveness, so the safety profile is covered. The description adds genuinely useful context beyond that: the matched secret value is redacted and never returned, which tells the agent what data it will and won't get back. It stops short of describing pagination or result volume.

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?

Two compact sentences, front-loaded with the action and scope, and the redaction caveat follows immediately. No redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only list tool with no output schema, the definition covers what is returned at a high level and flags the key data-handling fact (secret redaction). Missing only secondary details like pagination and default state filtering.

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 50%: org carries a description about the allowlist, while state is only an enum without prose. The description's field list (type, state, repo, location) refers to returned attributes rather than parameter behavior, so it adds little meaning beyond the schema's enum values.

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?

States a specific verb (List) and resource (organization's secret-scanning alerts) and enumerates the fields surfaced (type, state, repo, location). It is distinguishable from siblings by resource name, though it never explicitly contrasts itself with list_code_scanning_alerts or list_dependabot_alerts.

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 when-to-use guidance, no mention of prerequisites such as the org allowlist behavior for other org-scoped tools, and no routing to the code-scanning or dependabot siblings for other alert types. The only usage hint is the implicit state filter via the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.