
Exploring Information Security · 2026-04-14 · 35 min
Summary: Timothy De Block sits down with Casey Bleeker from SurePath AI to demystify the Model Context Protocol (MCP) . They discuss how this emerging standard allows Large Language Models (LLMs) to interact with external tools and why it represents a significant, often invisible, exposure risk for enterprises. Casey explains why MCP should be viewed like the HTTP protocol - ubiquitous and fundamental - and outlines the critical security controls needed to prevent data exfiltration and malicious code execution without blocking AI adoption. Key Topics Discussed What is MCP? MCP is a standard for creating a "natural language definition" of an API, allowing an LLM to intelligently determine when to call a specific tool rather than just generating text. It acts as a translation layer between a REST interface and the AI model, enabling the model to execute tasks like updating a CloudFormation stack or querying a database. The "HTTP" Analogy & Exposure Risk: Casey argues that MCP should be thought of as a protocol (like HTTP) rather than a specific tool.