How to Secure AI Agents on the MCP Protocol
MCP gives AI agents real tools, real credentials, and real blast radius. Here is a hardening guide for running MCP servers in production without torching your environment.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
MCP gives AI agents real tools, real credentials, and real blast radius. Here is a hardening guide for running MCP servers in production without torching your environment.
A senior engineer's threat model for Claude MCP tool poisoning in 2026, covering malicious servers, description hijacking, and the authorization patterns that actually help.
A senior engineer's take on the confused deputy problem in AI agent tool use, why it keeps reappearing in 2026, and the architectural patterns that actually fix it.
MCP servers are privileged dependencies. An inventory that tracks them like SBOM tracks packages is the minimum bar — and not every tool meets it.
The Safeguard MCP Server is publicly available and works with Claude Desktop, claude.ai, Claude Code, ChatGPT, Cursor, Gemini, and Grok. Here is the tool surface.
Claude Desktop's MCP support makes it a capable security tool. Griffin AI builds on that foundation rather than competing with it.
MCP servers connect AI agents to your infrastructure. Here's how to secure them without killing the productivity gains.
AI agents are consuming APIs, installing packages, and executing code autonomously. The security implications are massive and largely unaddressed.
Most MCP threat models confuse protocol risk with deployment risk. Here is what the real attack surface looks like after a year of production incidents.
Weekly insights on software supply chain security, delivered to your inbox.