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
The GitHub MCP Server connects AI tools directly to GitHub's platform. This gives AI agents, assistants, and chatbots the ability to read repositories and code files, manage issues and PRs, analyze code, and automate workflows. All through natural language interactions.
@@ -1315,7 +1317,7 @@ docker run -i --rm \
1315
1317
1316
1318
## Lockdown Mode
1317
1319
1318
-
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.
1320
+
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.
1319
1321
1320
1322
```bash
1321
1323
./github-mcp-server --lockdown-mode
@@ -1330,7 +1332,20 @@ docker run -i --rm \
1330
1332
ghcr.io/github/github-mcp-server
1331
1333
```
1332
1334
1333
-
At the moment lockdown mode applies to the issue read toolset, but it is designed to extend to additional data surfaces over time.
1335
+
The behavior of lockdown mode depends on the tool invoked.
1336
+
1337
+
Following tools will return an error when the author lacks the push access:
1338
+
1339
+
-`issue_read:get`
1340
+
-`pull_request_read:get`
1341
+
1342
+
Following tools will filter out content from users lacking the push access:
0 commit comments