Snyk Agent Scan provides a way to discover and inspect local agent components like Model Context Protocol (MCP) servers and skills. It identifies various security risks, such as prompt injections, malware payloads in natural language, sensitive data exposure, and credential leaks. The tool offers both an interactive command-line interface for individual users and a background mode for enterprise monitoring through Snyk Evo.
- Detects 15+ distinct security risks across MCP servers and agent skills
- Supports agents including Claude Code, Cursor, Windsurf, and Gemini CLI
- Automatically discovers configurations for various desktop and IDE-based agents
- Scanning MCP configs executes commands defined in them to retrieve tool descriptions
- Detects 15+ distinct security risks across MCP servers and agent skills
- Supports agents including Claude Code, Cursor, Windsurf, and Gemini CLI
- Automatically discovers configurations for various desktop and IDE-based agents
- Scanning MCP configs executes commands defined in them to retrieve tool descriptions
The Kaseya 2026 SaaS Security Report highlights critical vulnerabilities in cloud environments. A major concern is the rise of unmanaged guest accounts which now outnumber licensed users, providing expanded attack surfaces for credential-based attacks. Furthermore, OAuth integrations allow third-party applications to maintain persistent access even after passwords are changed, while low MFA enforcement leaves many accounts vulnerable to phishing and theft. The report also notes that external file sharing creates long-term data exposure risks and attackers increasingly use trusted infrastructure like VPNs to hide their activities from detection.
* Proliferation of unmanaged guest accounts
* Persistent access through OAuth integrations
* Widespread lack of MFA enforcement in SaaS environments
* Ongoing data exposure via orphaned file-sharing links
* Difficulty detecting malicious logins using trusted IP addresses
* Proliferation of unmanaged guest accounts
* Persistent access through OAuth integrations
* Widespread lack of MFA enforcement in SaaS environments
* Ongoing data exposure via orphaned file-sharing links
* Difficulty detecting malicious logins using trusted IP addresses
Researchers have identified a significant security flaw in Anthropic's Model Context Protocol, which is designed to connect Large Language Models with external tools. The protocol's architecture allows for remote command execution because the parameters used to create server instances can contain arbitrary commands that are executed in a server-side shell without proper input sanitization. This vulnerability has been demonstrated on platforms like LettaAI, LangFlow, Flowise, and Windsurf. When researchers brought these findings to Anthropic, the company responded that there was no design flaw and stated it is the developer's responsibility to implement sanitization.
Key points:
- MCP architecture facilitates remote command execution (RCE) via StdioServerParameters.
- Lack of input sanitization allows arbitrary commands and arguments in server-side shells.
- Exploitation has been successful against LettaAI, LangFlow, Flowise, and Windsurf.
- Anthropic maintains the protocol works as designed, placing responsibility on developers for security implementation.
Key points:
- MCP architecture facilitates remote command execution (RCE) via StdioServerParameters.
- Lack of input sanitization allows arbitrary commands and arguments in server-side shells.
- Exploitation has been successful against LettaAI, LangFlow, Flowise, and Windsurf.
- Anthropic maintains the protocol works as designed, placing responsibility on developers for security implementation.
This article details significant security vulnerabilities found in the Model Context Protocol (MCP) ecosystem, a standardized interface for AI agents. It outlines six critical attack vectors – OAuth vulnerabilities, command injection, unrestricted network access, file system exposure, tool poisoning, and secret exposure – and explains how Docker MCP Toolkit provides enterprise-grade protection against these threats.
This article details the Model Context Protocol (MCP), an open standard for connecting AI agents to tools and data across enterprise landscapes. It covers MCP implementations by AWS, Azure, and Google Cloud, security considerations, and the growing ecosystem surrounding the protocol.
The article details five security vulnerabilities in the Model Context Protocol (MCP): Tool Poisoning, Rug-Pull Updates, Retrieval-Agent Deception (RADE), Server Spoofing, and Cross-Server Shadowing. It explains how these vulnerabilities could compromise user safety and data integrity in AI agent systems.
Researchers from AWS and Intuit have designed a zero-trust security framework for the Model Context Protocol (MCP), addressing threats like tool poisoning and unauthorized access through multi-layered defenses including Just-in-Time access control and behavior-based monitoring.
