AI Runtime Security Series — Article #4
The Model Context Protocol (MCP) is rapidly becoming the standard for connecting AI agents to external tools, databases, and APIs. Adopted by Anthropic, OpenAI, and the broader agent ecosystem, MCP promises a unified interface for tool discovery and invocation. But beneath the elegant JSON-RPC abstraction lies a protocol-level security model built on trust — and trust is not a security boundary.
This article unpacks the readOnlyHint vulnerability, a design-level flaw in the MCP specification that allows any server to declare destructive tools as "read-only" without enforcement. We then trace how this flaw compounds across the entire MCP ecosystem, examine real CVEs discovered in production frameworks, and provide a concrete security checklist for teams deploying MCP-based agents.
1. The readOnlyHint: A Security Illusion
The MCP specification defines a readOnlyHint field on tool definitions:
