> The problem I have with articles like this and people commenting is that it's framed as if MCP's vulnerability (...)
You're extrapolating. The problem is clearly described as a MCP exploit, not a vulnerability. You're the only one talking about vulnerabilities. The system is vulnerable to this exploit.
It's not even an exploit. MCP is doing what it is MADE TO DO. It's made for interacting with the GitHub API. Whatever it has access to, it will access. If it has access to delete the repo, it will delete the repo. If it has access to the private repo, it will access the private repo.
> It's not even an exploit. MCP is doing what it is MADE TO DO.
You still don't understand the problem, do you? I mean, do you even understand the concept of an exploit?