Account suspension after using GitHub MCP

Open
  • Is something wrong?
#3,497 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
github, go
Domain
api, security

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Go
Stars
34.2k
Forks
5.3k
Avg merge
5d 18h
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/github-mcp-server

All issues in github/github-mcp-server

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.