Account suspension after using GitHub MCP

Aberta
  • Algo errado?
#3,497 0 comentários 1 reação 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
8/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
github, go
Domínio
api, security

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Go
Estrelas
34.2k
Forks
5.3k
Merge médio
5d 18h
PRs com merge (30d)
13

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de github/github-mcp-server

Todas as issues de github/github-mcp-server

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.