list_code_scanning_alerts

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.

Why list_code_scanning_alerts is rated Low

This tool retrieves and displays code scanning alerts from GitHub. It is purely a data query operation that does not modify state, execute code, or trigger external actions. The worst-case misuse would be information disclosure of already-visible security alerts, which is low severity in a GitHub context where such alerts are typically accessible to repository members.

From the tool's definition Tool name contains 'list' and description states 'List code scanning alerts' — these are unambiguous retrieval operations with no side effects. The tool queries existing security alert data without modifying, deleting, or executing anything.

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:

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

Questions about list_code_scanning_alerts