Fix issue triage repository guard#3089
Open
RickWinter wants to merge 1 commit into
Open
Conversation
Encode the explicit repository allowlist as an array so the MCP gateway can initialize the GitHub guard policy. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6e1020e5-dc4b-4e1e-8004-01f33a6b3977
RickWinter
requested review from
JasonYeMSFT,
alzimmermsft,
anannya03,
g2vinay,
jongio,
joshfree and
sandeep-sen
July 17, 2026 21:06
|
Azure Pipelines: Successfully started running 1 pipeline(s). There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Issue Triage Agent’s GitHub MCP guard configuration to use an explicit repository allowlist array (as required by the MCP gateway policy format), and regenerates the compiled lock workflow so the emitted policy contains "repos": ["microsoft/mcp"].
Changes:
- Change
allowed-reposfrom a scalar expression to an explicit array containingmicrosoft/mcp. - Regenerate the
issue-triage-agent.lock.ymloutput so the MCP gateway config emitsreposas an array and updates derived guard-policy values accordingly.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/issue-triage-agent.md |
Switches the GitHub tool guard allowed-repos to an explicit array (["microsoft/mcp"]) to satisfy gateway policy expectations. |
.github/workflows/issue-triage-agent.lock.yml |
Regenerated compiled workflow reflecting the new guard policy ("repos": ["microsoft/mcp"]) and related derived policy strings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
The Issue Triage Agent fails before startup because the MCP gateway accepts explicit repository allowlists only as arrays. Change the GitHub tool guard from a scalar repository expression to
["microsoft/mcp"], preserving least-privilege access while producing a valid gateway policy.Regenerate the gh-aw lock workflow with strict compilation. The generated policy now emits
"repos": ["microsoft/mcp"].GitHub issue number?
Fixes: #3040
Pre-merge Checklist
servers/Azure.Mcp.Server/README.mdand/orservers/Fabric.Mcp.Server/README.mddocumentationREADME.mdchanges running the script./eng/scripts/Process-PackageReadMe.ps1. See Package READMEToolDescriptionEvaluatorand obtained a score of0.4or more and a top 3 ranking for all related test promptsconsolidated-tools.jsonbreaking-changelabelservers/Azure.Mcp.Server/docs/azmcp-commands.md./eng/scripts/Update-AzCommandsMetadata.ps1to update tool metadata inazmcp-commands.md(required for CI)servers/Azure.Mcp.Server/docs/e2eTestPrompts.mdcrypto mining, spam, data exfiltration, etc.)/azp run mcp - pullrequest - liveto run Live Test PipelineThe MCP tool and Azure MCP Server checklist sections are not applicable because this changes only repository automation.
Invoking Livetests
Copilot submitted PRs are not trustworthy by default. Users with
writeaccess to the repo need to validate the contents of this PR before leaving a comment with the text/azp run mcp - pullrequest - live. This will trigger the necessary livetest workflows to complete required validation.