Approval gate
A hard checkpoint in an automated flow where execution stops until a human decides — distinct from a notification, which informs without stopping anything.
Gates belong wherever an action is irreversible or outward-facing: enrolling people into a sequence, sending any message, changing live campaign copy. The engineering point is that a gate must be structural — enforced by the system that executes, not promised by the model that plans. An agent that pinky-swears to ask first is a notification; a queue the send physically cannot bypass is a gate.
LinkedBoost is the LinkedIn MCP for Claude — agent-run outreach with enforced limits and a human trigger on every send. See how it works →