docs: document automatic minimum-integrity-approved guard policy for public repos#21298
Merged
docs: document automatic minimum-integrity-approved guard policy for public repos#21298
Conversation
…vior for public repos Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update automatic lockdown documentation for public repositories
docs: document automatic minimum-integrity-approved guard policy for public repos
Mar 16, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Documents the new runtime default guard behavior where public repositories using the GitHub MCP server receive an automatic min-integrity: approved policy when no explicit lockdown/min-integrity is configured.
Changes:
- Added an “Automatic Minimum-Integrity Protection” section explaining when
min-integrity: approvedis auto-applied and how to override it. - Added a guard policy callout in the GitHub tools reference linking to the new lockdown-mode documentation.
- Updated the lockdown-mode FAQ to distinguish automatic
min-integrity: approvedbehavior from traditional lockdown mode behavior.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| docs/src/content/docs/reference/lockdown-mode.md | Adds primary documentation for the automatic min-integrity: approved default and opt-out guidance. |
| docs/src/content/docs/reference/github-tools.md | Adds a guard policy note pointing readers to the new automatic behavior documentation. |
| docs/src/content/docs/reference/faq.md | Extends the FAQ answer to mention the new automatic min-integrity: approved behavior. |
| docs/src/content/docs/agent-factory-status.mdx | Updates the agent factory workflow list (Smoke Agent entries and removal of a removed workflow). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
|
|
||
| The automatic guard policy does **not** apply when: | ||
| - An explicit `lockdown` or `min-integrity` value is set in the workflow frontmatter. | ||
| - A GitHub App token is configured (`tools.github.app`). |
|
|
||
| Restrict which repositories and integrity levels the GitHub MCP server can access during agent execution. Guard policies apply fine-grained access control at the MCP gateway level. | ||
|
|
||
| For **public repositories** without explicit guard policy configuration, `min-integrity: approved` is applied automatically at runtime, ensuring content is filtered to owners, members, and collaborators even without additional authentication. See [Automatic Minimum-Integrity Protection](/gh-aw/reference/lockdown-mode/#automatic-minimum-integrity-protection) for details. |
Comment on lines
206
to
+208
| Lockdown mode is **automatically enabled** for public repositories if [Additional Authentication for GitHub Tools](/gh-aw/reference/github-tools/#additional-authentication-for-github-tools) is configured. It is not in effect for private or internal repositories. | ||
|
|
||
| In addition, for **public repositories** where the GitHub MCP server is not explicitly configured with `lockdown` or `min-integrity`, `min-integrity: approved` is automatically applied at runtime. This provides equivalent protection — restricting content to owners, members, and collaborators — even without additional authentication. |
Comment on lines
+15
to
+16
| For **public repositories** where the GitHub MCP server is configured **without** explicit `lockdown` or `min-integrity` guard policy settings, `min-integrity: approved` is automatically applied at runtime. This ensures the guardrail is always in place — even when additional authentication has not been configured. | ||
|
|
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.
Public repositories using GitHub MCP without explicit
lockdownormin-integrityconfiguration now automatically receivemin-integrity: approvedat runtime — but this behavior was undocumented.Changes
reference/lockdown-mode.md: Added "Automatic Minimum-Integrity Protection" section covering the new default, which repos it applies to, exclusions (explicit config, GitHub App token), and how to opt out.reference/github-tools.md: Added callout in the Guard Policies section noting the automatic behavior for public repos with a link to the new section.reference/faq.md: Extended the lockdown FAQ answer to distinguish between traditional lockdown mode (requires custom token) and the new automaticmin-integrity: approved(no additional auth needed).Key behavior documented
min-integrity: approved(automatic)min-integrity: noneTo disable the automatic guard policy on a public repo workflow that intentionally processes all user input:
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
telemetry.astro.build/opt/hostedtoolcache/node/24.14.0/x64/bin/node node /home/REDACTED/work/gh-aw/gh-aw/docs/node_modules/.bin/astro build(dns block)/opt/hostedtoolcache/node/24.14.0/x64/bin/node node /home/REDACTED/work/gh-aw/gh-aw/docs/node_modules/.bin/astro build tion instructio(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.