AI Pulse · AI Trends Pulse

Rippling just launched its own MCP gateway, and the backstory is worth knowing even if you never touch agent infrastructure directly. An MCP gateway is the control layer that sits between AI agents and your business tools like your HR system, your CRM, your accounting software. It decides what an agent is allowed to see and do. Runlayer sued Rippling in late July, claiming Rippling built its gateway using shared engineering access to Runlayer’s own product. Three weeks later, Runlayer dropped the suit. Rippling shipped the gateway anyway and is now counter-suing on patent grounds, according to the original report.

Here’s why this matters beyond the courtroom drama. This is the first real intellectual property fight to break out inside agent infrastructure, and it tells you something important. Companies are treating MCP gateways as defensible, ownable technology now, not generic plumbing anyone can build in a weekend. That shift changes how you should think about the vendors you’re evaluating for AI agent work. If gateways are becoming proprietary battlegrounds, expect more lock-in, more legal noise, and more pressure on smaller players who can’t afford to fight patent suits.

For a business owner, the practical takeaway is simple. Whoever controls the gateway between your data and your AI agents controls a lot more than plumbing. It’s worth asking any vendor you’re evaluating how they handle that layer, who owns it, and what happens if they get bought out or sued. This is the kind of control and visibility question we think about constantly when we build out an AI command centre for a business, because the gateway layer is where trust either holds or breaks. The legal fight isn’t settled, but the signal is already clear.