Adding Push to MCP: A New Attack Surface and a Design Sketch
braelyn_ai · x · 2026-10-28
The author notes MCP only lets agents pull; services cannot push without the user asking or waiting for a heartbeat, blocking features like "discuss this with your agent."
Proposed design:
- a server declares a push capability;
- the user grants it per server and per event type;
- the client turns each push into a new agent turn marked as untrusted data;
- the client enforces rate limits.
The author calls it a whole new attack surface, but a potentially major improvement to a widely adopted standard; Claude Code's "channels" is close but not universal.
Related event: Developers Flag MCP's Missing Push Mechanism and Design Fixes(2 posts)→
More from coding & agent
- ai-design-skills rockets to 9.1k GitHub stars with 1,395 stars in a single day — elayadesign · 2026-10-28
- EmbeddingGemma2 Turned Into a 20ms Real-Time Trainable Multimodal Endpoint on CPU — michellechen · 2026-10-28
- Anthropic hiring manager kills the coding interview: "It no longer provides signal" — felixrieseberg · 2026-10-28
- Nous' memelord Goes Beyond Research, Now Hookable via MCP — alexcovo_eth · 2026-10-28
- Custom node pack brings looping H3 video generation to Comfy Cloud — PurzBeats · 2026-10-28
- Chaosfolk: open-source tool sics 16 AI personas on your web app to break it — Vjeux · 2026-10-28