Account suspension after using GitHub MCP
維護者通常 2 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
The payload names no source files, tests or entry points, so there is no obvious place to start. It links three related rate-limit reports (#2037, #2233, #933) and describes an account suspension, which is an enforcement question beyond this repository's code. Done would mean a maintainer-agreed scope, such as documenting current rate-limit behaviour or proposing client-side throttling, not a code patch. Discuss the scope with maintainers before writing anything.
由索引模型根據 Issue 內容生成。
描述
Account suspension after using GitHub MCP
I was using the official GitHub MCP integration through ChatGPT to perform normal, authorized operations on my own GitHub account.
Shortly afterward, my account was suspended without warning.
There are already open reports related to MCP request/rate-limit behavior, including:
- #2037 — No built in safeguard against getting rate limited
- #2233 — Missing built-in rate limits/access controls
- #933 — Rapid API quota consumption through MCP activity
Security impact
If normal use of an authorized GitHub integration can generate activity that triggers account-level suspension, this creates an account availability and enforcement-safety issue.
A legitimate user can effectively lose access to their account as a consequence of request behavior generated by an official integration that the user does not control.
The user does not control the MCP request cadence, concurrency, retry strategy, API behavior, or GitHub's enforcement mechanisms.
GitHub controls both the MCP implementation and the enforcement systems behind the API. These systems should have safeguards preventing legitimate MCP activity from escalating into an account-level lockout or suspension.
This should therefore be reviewed not only as a rate-limiting issue, but as a security/reliability boundary problem between an authorized client and GitHub's account enforcement systems.
Please review the interaction between MCP request behavior, rate limiting, abuse detection, and account-level enforcement.
- 主要語言
- Go
- 星號
- 34.2k
- 分支
- 5.3k
- 平均合併
- 5 天 18 小時
- 30 天內合併 PR
- 13
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/github-mcp-server 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 69/100
github/github-mcp-server#3760 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
github/github-mcp-server#3758 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 69/100
github/github-mcp-server#3729 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 65/100
github/github-mcp-server#3722 ·
維護者通常 2 天內回覆
-
Insiders Feedback: PR created UI doesn't link to the PR可能已有人在做 @genius-0963 於 5 天前認領。 未關閉bug insiders user-experience
難度 2/5 1-3 小時 新手友好度 65/100
github/github-mcp-server#3658 ·
維護者通常 2 天內回覆
查看 github/github-mcp-server 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 72/100
open-feature/flagd-schemas#237 ·
-
enhancement
難度 2/5 1-3 小時 新手友好度 72/100
superplanehq/superplane#9234 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 65/100
betterleaks/betterleaks#469 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
prime-radiant-inc/evener#5901 ·
維護者通常 1 天內回覆