The key is, it's not the person who grants the MCP access who is the attacker.
The attacker is some other person who can create issues on a public Repo but has no direct access to the private repo.
The attacker is some other person who can create issues on a public Repo but has no direct access to the private repo.
You're the only one talking about GitHub MCP vulnerabilities. Everyone else is talking about GitHub MCP exploits. It's in the title, even.