Lessons from a LinkedIn MCP server that takes real actions

Calm_Ambassador9932 · reddit · 2026-11-13

The We-Link team shares design lessons from building an MCP server that acts on LinkedIn (search, connection requests, messages): confirm before irreversible actions; deliberately slow 10–60s human-paced execution with rate limits in the server, not the prompt; never put credentials in chat (separate secure sign-in link, removing the connector cuts access); explain destructive tools before asking for confirmation; and state limits in tool descriptions so the model says "I can't" instead of hallucinating. Open questions: where confirmation should live (server/client/model) and how to handle long-running actions in fast-response clients.

Original post →

More from coding & agent

coding & agent channel →