MCP is just one protocol, there are already others like A2A etc which will do similar. And there is a raw form of this, tell the LLM to read the GitHub API docs

MCP is just one protocol, there are already others like A2A etc which will do similar. And there is a raw form of this, tell the LLM to read the GitHub API docs and use it as needed, using this auth token). I don't know if any LLM is powerful enough to do this yet, but they definitely will be. I don't think there is really a way to secure all these tool registration mechanisms, especially when it's the LLM at fault in the end of leaking data. People do want to use LLMs to improve their productivity - LLMs will either need provable safety measures (seems unlikely to me) or orgs will need to add security firewalls to every laptop, until now perhaps developers could be trusted to be sophisticated but LLMs definitely can't. Though I'm not sure how to reason on the end result if even the security firewalls use LLMs to find bad behaving LLMs...