You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1264,7 +1264,7 @@ docker run -i --rm \
1264
1264
1265
1265
## Lockdown Mode
1266
1266
1267
-
Lockdown mode limits the content that the server will surface from public repositories. When enabled, requests that fetch issue details will return an error if the issue was created by someone who does not have push access to the repository. Private repositories are unaffected, and collaborators can still access their own issues.
1267
+
Lockdown mode limits the content that the server will surface from public repositories. When enabled, the server checks whether the author of each item has push access to the repository. Private repositories are unaffected, and collaborators keep full access to their own content.
1268
1268
1269
1269
```bash
1270
1270
./github-mcp-server --lockdown-mode
@@ -1279,7 +1279,20 @@ docker run -i --rm \
1279
1279
ghcr.io/github/github-mcp-server
1280
1280
```
1281
1281
1282
-
At the moment lockdown mode applies to the issue read toolset, but it is designed to extend to additional data surfaces over time.
1282
+
The behavior of lockdown mode depends on the tool invoked.
1283
+
1284
+
Following tools will return an error when the author lacks the push access:
1285
+
1286
+
-`issue_read:get`
1287
+
-`pull_request_read:get`
1288
+
1289
+
Following tools will filter out content from users lacking the push access:
0 commit comments