MCP, auth & payments

MCP Security & Tool Poisoning

The security risks behind the apps an AI assistant can plug into, and why a trusted one keeps your in-chat leads safe


When an AI assistant plugs into an outside app, that app can hand it instructions, not just data. Tool poisoning is when someone hides bad instructions inside a tool so the assistant does something it shouldn't — leak data, call the wrong action, mislead the buyer.

It's the security conversation around the Model Context Protocol, the standard that lets assistants like ChatGPT and Claude use third-party apps.

Why it matters for the ChatGPT funnel

The whole point is to be the app the assistant picks at the moment of buyer intent. A poisoned or sloppy connector breaks that trust fast — and a flagged app gets pulled, taking your in-chat pipeline with it.

You don't need the protocol details. You do need the one thing that follows from this: the app booking your leads has to be locked down, or it never makes it in front of buyers.

How drio fits

This is the part you don't have to think about. drio runs the server your buyers' assistant talks to, with the auth, isolation, and validation handled for you. You focus on turning AI-search demand into booked meetings. We keep the door it walks through clean.

Win the answer, not just the ranking

drio turns the ChatGPT and Claude conversations your buyers are already having into booked calls. Build the app that gets you picked.

Sell inside ChatGPT