www.pento.ai
A Year of MCP: From Internal Experiment to Industry Standard | Pento
Excerpt
## The Hard Truth: Security Is Still the Elephant in the Room Let's be direct: MCP in 2025 shipped fast, and security didn't always keep pace. Security researchers have documented multiple outstanding issues, and some are genuinely concerning:^10^ **Authentication gaps**: The protocol provides minimal guidance on authentication, and many implementations default to no auth at all. Session IDs in URLs violate basic security practices. Until recently, there was no official registry to verify server authenticity.^11^ **Prompt injection vulnerabilities**: Tool descriptions go straight to the AI model. Malicious actors can hide instructions in those descriptions that the AI follows without the user's knowledge.^12^ **Token storage risks**: MCP servers often store OAuth tokens for multiple services. One breach equals access to everything: your Gmail, your Drive, your CRM.^13^
Related Pain Points
AI agent security and blast radius management
9Production incidents show AI agents leaking internal data, shipping ransomware through plugins, and executing destructive actions (deleting repos). Security shifted from prompt injection to actual agent capabilities and operational risk.
Common Security Vulnerabilities in MCP Deployments
8Rapid MCP ecosystem growth has revealed common vulnerability patterns in deployed servers including command injection, insufficient input validation, privilege escalation, authentication implementation flaws, and lack of rate limiting.