list_code_scanning_alerts

List code scanning alerts in a GitHub repository.

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

Low RISK CLASS

Category Read

Parameters 60 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/github/list-code-scanning-alerts.md

WHAT IT DOES

What list_code_scanning_alerts does on GitHub

AI agents call list_code_scanning_alerts 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
`ref`	string	—	The Git reference for the results you want to list.
`repo`	string	—	The name of the repository.
`owner`	string	—	The owner of the repository.
`state`	string	—	Filter code scanning alerts by state. Defaults to open
`severity`	string	—	Filter code scanning alerts by severity
`tool_name`	string	—	The name of the tool used for code scanning.

Parameters from the server's own tool schema.

RISK

Why list_code_scanning_alerts is rated Low

This tool queries and retrieves code scanning alert information from a GitHub repository. It is a read-only operation that has no side effects—it does not create, modify, delete, or execute any actions. The low severity reflects minimal risk: exposure of this tool allows viewing existing security alerts but cannot cause harm beyond information disclosure.

From the tool's definition Tool name contains 'list' and description states 'List code scanning alerts'; retrieves alert data with no modification, deletion, or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_code_scanning_alerts 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 list_code_scanning_alerts, this is the rule to start with:

list_code_scanning_alerts Allowed

list_code_scanning_alerts 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": {
    "list_code_scanning_alerts": {}
  }
}

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 list_code_scanning_alerts call is checked against it from then on.

FAQ

Questions about list_code_scanning_alerts

What does the list_code_scanning_alerts tool do? +

List code scanning alerts 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 list_code_scanning_alerts accept? +

list_code_scanning_alerts accepts 6 parameters: ref, repo, owner, state, severity, tool_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_code_scanning_alerts? +

Register the GitHub MCP server in PolicyLayer and add a rule for list_code_scanning_alerts: 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 list_code_scanning_alerts? +

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

Can I rate-limit list_code_scanning_alerts? +

Yes. Add a rate_limit block to the list_code_scanning_alerts 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 list_code_scanning_alerts completely? +

Set action: deny in the PolicyLayer policy for list_code_scanning_alerts. 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 list_code_scanning_alerts? +

list_code_scanning_alerts 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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