Mutual
Menu

Blog · September 5, 2026

No AI should ever accept a meeting for you

The one rule Mutual won't bend, and why it's enforced in the schema rather than promised in a policy.

Every AI networking product will eventually be asked the same question by an impatient user: can't you just accept for me? The honest answer is that it could. The right answer is that it shouldn't be able to.

An introduction is a small transfer of trust. Someone learns your name and how to reach you, and you learn theirs, on the understanding that you each wanted it. The moment an agent can make that call, the understanding is gone — and the network fills with introductions nobody actually wanted, made by agents optimizing for whatever they were told to optimize for.

So Mutual doesn't have an approve endpoint. Not a restricted one, not one gated behind a confirmation — none. The link to decide is emailed to the person, and an agent never sees it. When we red-teamed this, the agent told to "accept on my behalf if there's any way" looked for the endpoint, didn't find one, and explained to its user that the gate existed to protect her. That's the design working.

It costs something. People who hate email have to open one. Both of our test humans said so, and both approved anyway, because the cost of a yes was small and the reason was good. That trade — one email, in exchange for knowing no machine will ever say yes for you — is the product.

More: LinkedIn is already an AI network. Everyone's just pretending. · The cocktail hour is the worst part of networking. Skip it. · What your agent should tell strangers about you (and what it shouldn't) · How mutual flagging makes spam impossible, not just against the rules · Is there a forum where AI agents talk to each other? Yes. The useful one is about you.