Skip to content

Add MCP tool naming guidance to security-fix-pr workflow #12022

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
mnkiefer merged 3 commits into from
Jan 27, 2026
Merged

Add MCP tool naming guidance to security-fix-pr workflow #12022

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5fc8743
Initial plan
Copilot Jan 27, 2026
203bcea
Add MCP tool naming guidance to security-fix-pr workflow
Copilot Jan 27, 2026
563d121
Merge branch 'main' into copilot/fix-mcp-tools-issue
mnkiefer Jan 27, 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
13 changes: 10 additions & 3 deletions .github/workflows/security-fix-pr.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

13 changes: 10 additions & 3 deletions .github/workflows/security-fix-pr.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,13 @@ timeout-minutes: 20

You are a security-focused code analysis agent that identifies and creates autofixes for code security issues using GitHub Code Scanning.

## Important Guidelines

**Tool Usage**: When using GitHub MCP tools:
- Always specify explicit parameter values: `owner` and `repo` parameters
- Do NOT attempt to reference GitHub context variables or placeholders
- Tool names use triple underscores: `github___` (e.g., `github___list_code_scanning_alerts`, `github___get_code_scanning_alert`)

## Mission

When triggered, you must:
Expand Down Expand Up @@ -64,7 +71,7 @@ Check if a security URL was provided:
- Skip to step 2 to get the alert details directly
- **If no security URL is provided**:
- Use the GitHub API to list all open code scanning alerts
- Call `list_code_scanning_alerts` with the following parameters:
- Call `github___list_code_scanning_alerts` with the following parameters:
- `owner`: ${{ github.repository_owner }}
- `repo`: The repository name (extract from `${{ github.repository }}`)
- `state`: "open"
Expand All @@ -75,7 +82,7 @@ Check if a security URL was provided:

### 2. Get Alert Details

Get detailed information about the selected alert using `get_code_scanning_alert`:
Get detailed information about the selected alert using `github___get_code_scanning_alert`:
- Call with parameters:
- `owner`: ${{ github.repository_owner }}
- `repo`: The repository name (extract from `${{ github.repository }}`)
Expand All @@ -90,7 +97,7 @@ Get detailed information about the selected alert using `get_code_scanning_alert
### 3. Analyze the Vulnerability

Understand the security issue:
- Read the affected file using `get_file_contents`:
- Read the affected file using `github___get_file_contents`:
- `owner`: ${{ github.repository_owner }}
- `repo`: The repository name (extract from `${{ github.repository }}`)
- `path`: The file path from the alert
Expand Down
Loading