Skip to content

Constrain list_code_scanning_alerts prompt usage with explicit state/severity bounds #43744

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 6 commits into from
Jul 6, 2026
Merged

Constrain list_code_scanning_alerts prompt usage with explicit state/severity bounds #43744

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
be748f5
Initial plan
Copilot Jul 6, 2026
01dfc99
Bound list_code_scanning_alerts prompt usage
Copilot Jul 6, 2026
98e1f6d
Harden list_code_scanning_alerts bounds regression test
Copilot Jul 6, 2026
51751a4
Document and enforce bounded code-scanning alert queries
Copilot Jul 6, 2026
31eed7e
Remove code_scanning_prompt_bounds_test.go
Copilot Jul 6, 2026
4ea7df3
Add bounded guidance to all list_code_scanning_alerts table mentions …
Copilot Jul 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .github/aw/github-mcp-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -204,6 +204,8 @@ The following toolsets are recommended as defaults for typical agentic workflows
| `get_code_scanning_alert` | Get details of a specific code scanning alert | `owner`, `repo`, `alert_number` |
| `list_code_scanning_alerts` | List code scanning alerts for a repository | `owner`, `repo`, `state`, `severity` |

When calling `list_code_scanning_alerts` in workflow prompts/templates, always bound requests with `state: open` and `severity: critical,high`.

---

### dependabot
Expand Down Expand Up @@ -368,4 +370,3 @@ Most toolsets work with the default `GITHUB_TOKEN` in GitHub Actions. Exceptions
- `projects` — Requires a PAT with `project` scope
- `security_advisories` (write) — Requires `security-events: write` permission
- `actions` (write for `actions_run_trigger`) — Requires `actions: write` permission

6 changes: 4 additions & 2 deletions .github/skills/github-mcp-server/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ The following toolsets are enabled by default when `toolsets:` is not specified:
| `issues` | Issue management | `issue_read`, `list_issues`, `create_issue`, `search_issues` |
| `pull_requests` | Pull request operations | `pull_request_read`, `list_pull_requests`, `create_pull_request` |
| `actions` | GitHub Actions/CI/CD | `list_workflows`, `list_workflow_runs`, `download_workflow_run_artifact` |
| `code_security` | Code scanning and security | `list_code_scanning_alerts`, `get_code_scanning_alert` |
| `code_security` | Code scanning and security | `list_code_scanning_alerts` ⚠️ (always include `state: open` and `severity: critical,high`), `get_code_scanning_alert` |
| `dependabot` | Dependency management | Dependabot alerts and updates |
| `discussions` | GitHub Discussions | `list_discussions`, `create_discussion` |
| `experiments` | Experimental features | Unstable/preview APIs |
Expand Down Expand Up @@ -173,6 +173,8 @@ This section maps individual tools to their respective toolsets to help with mig
- `get_code_scanning_alert` - Get details of a specific alert
- `create_code_scanning_alert` - Create a code scanning alert

When invoking `list_code_scanning_alerts` from workflow prompts/templates, always include `state: open` and `severity: critical,high`.

Copilot AI Jul 6, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in commit 4ea7df3 — the bounded state: open / severity: critical,high warning is now inlined in both the "All Available Toolsets" table and the allowed→toolsets migration table, in addition to the Code Security Toolset section.


### Discussions Toolset
- `list_discussions` - List discussions in a repository
- `create_discussion` - Create a new discussion
Expand Down Expand Up @@ -292,7 +294,7 @@ Use this table to identify which toolset contains the tools you need:
| `issue_read`, `list_issues`, `create_issue`, `update_issue`, `search_issues` | `issues` |
| `pull_request_read`, `list_pull_requests`, `create_pull_request` | `pull_requests` |
| `list_workflows`, `list_workflow_runs`, `get_workflow_run` | `actions` |
| `list_code_scanning_alerts`, `get_code_scanning_alert` | `code_security` |
| `list_code_scanning_alerts` ⚠️ (always include `state: open` and `severity: critical,high`), `get_code_scanning_alert` | `code_security` |
| `list_discussions`, `create_discussion` | `discussions` |
| `get_label`, `list_labels`, `create_label` | `labels` |
| `get_user`, `list_users` | `users` |
Expand Down
2 changes: 2 additions & 0 deletions docs/src/content/docs/guides/mcps.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,8 @@ The GitHub MCP server is built into agentic workflows and provides comprehensive
| `code_security` | Security alerts | `list_code_scanning_alerts` |
| `users` | User profiles | `get_me` ⚠️, `get_user`, `list_users` |

When calling `list_code_scanning_alerts` from workflow prompts, always bound the request with `state: open` and `severity: critical,high`.

The `default` toolset includes: `context`, `repos`, `issues`, `pull_requests`. When used in workflows, `[default]` expands to action-friendly toolsets that work with GitHub Actions tokens. Note: The `users` toolset is not included by default as GitHub Actions tokens do not support user operations.

> [!WARNING]
Expand Down
Loading