MODEL CONTEXT PROTOCOL (MCP) AND SUPPLY-CHAIN SECURITY

PROTOCOL-LEVEL WEAKNESSES Some weaknesses come from the design of the protocol and its ecosystem. One is the lack of capability attestation, which means a server can claim to do one thing, and there is no built-in, guaranteed proof that it does only that. A server's own description of its tools is just text it wrote about itself. Another weakness is weak vetting in registries, the public listings where servers are published. A listing may not have been carefully checked. A third is that tool descriptions flow straight into the model's context, which opens the door to the tool poisoning you learned about in Chapter 38. The protocol can be used safely, but safety must be added by the harness and by organizations.