Wallarm Research has just released a powerful new Nuclei template targeting a new kind of exposure: the Model Context Protocol (MCP). This isn’t about legacy devtools or generic JSON-RPC pinging. It’s about the protocol fueling next-gen LLM applications — and it’s already showing up exposed in the wild. What is Model Context Protocol? MCP, developed by Anthropic, introduces a standardized way for language model hosts to connect with external tools, prompts, and structured resources through JSON-RPC 2.0. Think of it as the USB-C for AI infrastructure: plug-in-anywhere simplicity, with deep execution power behind the scenes. The Model Context Protocol enables platforms like Claude Desktop to call toolchains, reference internal datasets, and generate responses based on dynamic prompt templates — all through a unified interface. And here’s the risk: as we explored in detail on modelcontextprotocol.io, these MCP servers are often exposed. What Is the Risk and How Does It Work? Wallarm's latest threat intelligence shows dozens of deployments where MCP backends have been unintentionally published to the internet — often by internal AI labs, fast-moving dev teams, or unsecured cloud-hosted experiments. The result: unauthenticated access to sensitive LLM control surfaces. From listing internal prompts and tools, to invoking operations directly, exposed MCP endpoints are a goldmine for adversaries. To visualize how this works under the hood: The host (an AI app or IDE) speaks to an…Read More