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
-
难度 2/5 1-3 小时 新手友好度 82/100
prime-radiant-inc/evener#5901 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 69/100
-
kind/bug
难度 2/5 1-3 小时 新手友好度 78/100
kyma-project/serverless#2769 ·
维护者通常 1 天内回复
-
ready-for-agent
难度 2/5 1-3 小时 新手友好度 78/100
hexlet-basics/hexlet-basics#962 ·
维护者通常 1 天内回复
-
imapproxy closeForMaintenance grace timer calls clientConn.Close() before closeMaintenanceTransport可能已有人在做 @dejanstrbac 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复