get_secret_scanning_alert

Get details of a specific secret scanning alert in a GitHub repository.

SERVERGitHub SOURCEoci:ghcr.io/github/github-mcp-server:1.3.0

Low RISK CLASS

Category Read

Parameters 30 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/github/get-secret-scanning-alert.md

WHAT IT DOES

What get_secret_scanning_alert does on GitHub

AI agents call get_secret_scanning_alert to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`repo`	string	—	The name of the repository.
`owner`	string	—	The owner of the repository.
`alertNumber`	number	—	The number of the alert.

Parameters from the server's own tool schema.

RISK

Why get_secret_scanning_alert is rated Low

This tool retrieves information about detected secrets without creating, modifying, or deleting data. It is categorized as Read because it performs a query operation. Severity is high because exposure of secret scanning alerts could reveal sensitive credentials and their locations in the codebase, enabling an attacker to locate and potentially exploit leaked secrets.

From the tool's definition Tool name and description indicate 'Get details of a specific secret scanning alert' — a retrieval operation with no modification. However, the data retrieved is sensitive (secret scanning alerts contain detected credentials/secrets).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_secret_scanning_alert safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_secret_scanning_alert, this is the rule to start with:

get_secret_scanning_alert Allowed

get_secret_scanning_alert is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_secret_scanning_alert": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every get_secret_scanning_alert call is checked against it from then on.

FAQ

Questions about get_secret_scanning_alert

What does the get_secret_scanning_alert tool do? +

Get details of a specific secret scanning alert in a GitHub repository. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

What parameters does get_secret_scanning_alert accept? +

get_secret_scanning_alert accepts 3 parameters: repo, owner, alertNumber. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_secret_scanning_alert? +

Register the GitHub MCP server in PolicyLayer and add a rule for get_secret_scanning_alert: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches GitHub. Nothing to install.

What risk level is get_secret_scanning_alert? +

get_secret_scanning_alert is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_secret_scanning_alert? +

Yes. Add a rate_limit block to the get_secret_scanning_alert rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block get_secret_scanning_alert completely? +

Set action: deny in the PolicyLayer policy for get_secret_scanning_alert. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides get_secret_scanning_alert? +

get_secret_scanning_alert is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 86 GitHub tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →