Home
Storia in 1 fonti
The MCP Confused Deputy: Provenance Gaps, Instruction Injection, and DNS Rebinding in the Model Context Protocol
MCP's tool-result schema carries no attestable provenance. ToolAnnotations are advisory, not security boundaries. The official fetch server pipes attacker-controlled content straight into model context. Here's the confused-deputy chain, the DNS rebin
Raccontata da
dev.to
Timeline cronologica
- ·
MCP Protocol Deep-Dive: How Tool Discovery Actually Works Under the Hood
MCP Protocol Deep-Dive: How Tool Discovery Actually Works Under the Hood Uncover the mechanics of...
- ·
The MCP Confused Deputy: Provenance Gaps, Instruction Injection, and DNS Rebinding in the Model Context Protocol
MCP's tool-result schema carries no attestable provenance. ToolAnnotations are advisory, not security boundaries. The official fetch server pipes attacker-controlled content…
- ·
Resources for reading, tools for acting: the MCP design choice most servers get wrong
Every tool you expose over MCP ships its full definition (name, description, JSON schema) into the...
- ·
A Postgres-Backed MCP Server in ~20 Lines
The Model Context Protocol is how an AI agent gets tools. You stand up an MCP server, it advertises a...