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:

• No built in safeguard against getting rate limited #2037 — No built in safeguard against getting rate limited
• Suggestion: add a recommended security policy / rate limiting guide #2233 — Missing built-in rate limits/access controls
• MCP server extension running up API requests and hitting user rate limits #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.