Account suspension after using GitHub MCP

Aperta
  • Qualcosa non va?
#3,497 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
github, go
Ambito
api, security

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

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.

Lingua principale
Go
Stelle
34.2k
Fork
5.3k
Merge medio
5g 18h
PR unite (30g)
13

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/github-mcp-server

Tutte le issue di github/github-mcp-server

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.