Use Case · Mistral Le Chat

Le Chat pulled confidential deal data. Then it emailed forty people.

Le Chat can read your CRM and send emails. Civic makes sure it respects data classifications, and gets approval before sending.

Start building See how it works

use case / mistral le chat

A board-level acquisition target ended up in forty inboxes.

Just imagine, one day…

A sales manager asks Le Chat to pull the latest deal pipeline from the CRM and email a summary to the VP of Sales. Le Chat does exactly that. It reads every deal, including one tagged “confidential: board only.”

The summary goes out. The VP forwards it to the full sales team. 40 people now have the name of a board-level acquisition target in their inbox. The CEO finds out from a Slack thread. The deal isn't dead, but the trust is.

The agent did what it was asked. It just couldn't read the label that said “stop.”

Without guardrails, Le Chat treats all CRM data the same.

It does things you did not intend

You asked for a pipeline summary. It included a board-level confidential deal. The CRM had the classification. The agent ignored it.

You cannot prove what happened

No log of which CRM fields it read, which deals it included, or whether it saw the confidential tag. You're re-reading the email to figure out what leaked.

You cannot stop it fast enough

Email is instant and irreversible. Once Le Chat hits send, you can't unsend it. The VP forwarded it in 2 minutes. 40 inboxes in 5.

It gets confused and you never know

The CRM marks deals as confidential using a custom field. Le Chat doesn't know which fields are access controls and which are metadata. It reads everything.

Le Chat calls Civic. Civic filters the data and approves the actions.

Connectivity

One MCP endpoint for your CRM, email, calendar, and documents. Le Chat connects to business tools through Civic. No direct API keys in the chat config.

Guardrails

Read deals, generate summaries, draft emails. But no access to confidential deals, no email sends without approval, no bulk exports.

Auditability

Every CRM read, every email draft, every send logged with the full content and recipient list. See what data the agent accessed before it leaves your system.

Revocation

Revoke any connection and Le Chat loses access to CRM, email, and every connected tool. Instant disconnect across the whole team.

Connect Le Chat through Civic in three steps

Mistral Le Chat Agent

Add CRM and email.

Filter out deals marked confidential.

Require approval before email sends.

Block bulk data exports.

Done. 2 tools connected:

✓ CRM — read deals (no confidential)

✓ Email — draft + send (approval req.)

Your MCP URL is ready to copy.

Read the docs

The same scenario. Different outcomes.

Without Civic, Le Chat reads everything and sends immediately. With Civic, confidential data is filtered and sends require approval.

$ le-chat: pull the deal pipeline and email the VP

[le-chat] reading CRM — 47 deals

[le-chat] summarizing... (includes confidential deal)

[email:send] summary sent to VP

[email:forward] VP forwarded to 40 people

$ # board-level deal in 40 inboxes. irreversible.

$ le-chat: pull the deal pipeline and email the VP

[le-chat] reading CRM via Civic — 46 deals

[nexus] 1 deal filtered (confidential: board only)

[le-chat] summarizing 46 deals...

[le-chat] requesting email send to VP...

[nexus] ⏸ HELD — email send requires approval

[nexus] preview sent to sales-mgr for review

$ # confidential deal excluded. email pending approval.

Le Chat handles your data. Civic makes sure it respects the labels.

Your team uses AI for real business work. Spend 10 minutes making sure confidential data stays confidential.

Start building Read the docs