MCP tool annotations are hints, not guarantees
The MCP spec says clients must treat tool annotations as untrusted unless the server is trusted. What that means for approval logic and auto-run rules.
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.
The MCP spec says clients must treat tool annotations as untrusted unless the server is trusted. What that means for approval logic and auto-run rules.
Stolen MCP tokens look like legitimate requests. The spec asks for secure storage, short-lived access tokens and refresh rotation. Details and a checklist.
How the resource parameter from RFC 8707 binds an MCP access token to one server, and what an MCP server must check before trusting a token.
MCP servers must not use sessions for authentication. Learn the two session hijack attacks and how to bind session IDs to the authenticated user.
The MCP tools spec says servers must validate inputs, enforce access control, rate limit and sanitize outputs. A practical checklist for building a tool.
Local MCP servers over HTTP can be reached from a website through DNS rebinding. The spec requires Origin validation and recommends binding to localhost.
An MCP proxy with a static client ID and a consent cookie can hand an attacker an authorization code. Learn the four conditions and the required fixes.
A malicious MCP server can point OAuth discovery URLs at internal services and cloud metadata. The spec lists the defenses clients should apply.
A hostile MCP server can send a javascript: or shell-laced authorization URL. Clients must allow only http and https and never open URLs through a shell.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.