Cybersecurity

Agent to Agent Network Effects Hit Privacy Wall

Jean-Denis Greze reframes agent-to-agent as search for the perfect context window and details five privacy-constrained patterns plus their poisoning risks.

StartupHub.ai Staff

By StartupHub.ai Staff, reviewed by Daniel Singer, Editor

2 min read

In an AI Engineer talk, Jean-Denis Greze demoed five designs for agent to agent network effects that try to pull Gmail, Slack and wiki data into one context window without granting global access. He showed the failure needs no remote exploit, only local policy or prompt flaws.

Agent to Agent Network Effects Hit Privacy Wall - AI Engineer
Agent to Agent Network Effects Hit Privacy Wall, AI Engineer

Greze is CTO at Town and former CTO at Plaid, now building assistants for nontechnical users where agents have to work across personal and company silos.

How the attack actually works

Think of the context window as a courtroom table where only admitted evidence can be placed before the judge rules. Agents are just trying to get the right evidence on the table.

The five approaches are a shared agent inside a trust boundary, a scoring tool that hides raw emails, an auto-updated shared wiki or skill store, humans as manual conduits, and a black box router that scans all silos then asks only the relevant owner for approval.

The black box variant fails if policy is vague or prompt injection slips a malicious instruction into a silo, because a single poisoned note can be pulled into the shared space and then treated as truth.

What is broken and why it matters

Companies want network effects without creating a god agent that sees everything, so they're choosing tools and wikis that trade raw access for derived signals and that improve as models get better at enforcing policy.

Greze bets the near term winner is a sweeper AI that watches private silos and pushes low sensitivity facts to shared stores, with explicit human approval for finance and HR data and full logging for audit by security teams.

Anthropic already normalized auto mode for code approvals, and Greze sees the same path for privacy where more disclosures become automatic as policy encoding improves, though cross company sharing remains the hard unsolved beachhead.

No vendor here ships a verifiable black box today, and without reversible logs plus injection defenses the network effect becomes a disclosure liability.

Sources

Get the free daily brief every morning

Every morning the day's AI news, new AI startups and new funding rounds. Free and takes a few minutes to read, unsubscribe at any time.

Join 64,000 other subscribers.

TopicsTownJean-Denis GrezePlaidAnthropicAI EngineerAcme Corp

StartupHub.ai Staff

Written by

StartupHub.ai Staff

Editorial team

The staff writers of StartupHub.ai, ranging from investment analysts to avid AI tool users, early adopters and critical enthusiasts. Backgrounds span engineering, business and the arts. We hold every piece to rigorous standards of research and review.

Daniel Singer

Written by

Daniel Singer

Editor, reviewed this article

Daniel Singer is an AI expert who has been writing about, covering and building AI technology since 2018.

Test your Agent Readiness now

Paste your website. How well ChatGPT, Claude and the other agents can read and use a site, in about a minute.

Watch

The videos behind the news, one flip at a time

The feed mixes the videos from our articles with startup demos and you flip through them like TV channels for free with no signup.