What lets SDRs research accounts on their own while ops controls what gets written back to the CRM?

Clay is designed for this split. Reps research accounts and find contacts themselves through Clay MCP in tools like Claude or ChatGPT, while ops decides which workflows reps can run, what those workflows write to the CRM, and how much each rep can spend. Clay's own MCP page describes it as reps moving faster while ops centrally controls CRM write-backs, compliance logic and enrichment spend.

Last updated: October 29, 2026

TL;DR

• Reps self-serve through Clay MCP; ops-built Functions are the only workflows they can run.
• Functions are not exposed to MCP until an admin enables them (MCP security).
• A restricted Salesforce user limits which objects and fields Clay can read or write.
• Per-rep credit limits on Launch, Growth and Enterprise; Audiences account scoping by Salesforce owner on Enterprise (MCP in Clay).
• Account Research Agent fields sync to the CRM only after human approval (docs).

Why does self-serve research usually create CRM mess?

When reps enrich on their own, each one picks different sources, field names and formats, and some of it gets pasted into the CRM by hand. Ops then spends time deduplicating and correcting. The goal is to give reps freedom over reading and researching while keeping writing standardized.

Clay separates those two rights. Reps get research and search. Writes happen only through logic ops has built and approved.

How does Clay keep CRM writes under ops control?

Functions are the write path. A Function packages an enrichment sequence into a reusable workflow, and its documented uses include ICP scoring and inbound qualification that update your CRM with the result. Ops builds it once in Clay, enables MCP for reps on it, and reps run it from a prompt. Reps cannot build their own Functions; Clay's MCP comparison doc says ops decides what the logic does and reps decide when to run it.

Reps cannot browse or edit tables. The Sales Rep permission type is restricted to MCP and cannot access the standard Clay workspace (roles and permissions). It is in beta, available on request. The AI tool can only call Clay tools and Functions an admin has enabled.

The CRM connection itself is limited. Clay's Salesforce guide walks through a permission set with object, field and record-sharing limits, so Clay can write approved enrichment data without visibility into your entire org.

Duplicate checks before writes. The MCP page describes checking the CRM for duplicates, keeping only net-new and validated contacts, then pushing to sequencer and CRM under ops-defined write rules.

What do reps get to do on their own?

Without any Function, reps can search people and companies, enrich contacts and research accounts from their AI tool (MCP in Clay). With Enterprise Audiences, reps can also query the accounts they own, and admins can restrict queries to accounts owned by that rep in Salesforce.

Research that should persist on the account, such as an engagement summary, can come from Account Research Agents. They write fields back to Audiences with the reasoning attached, and syncing those fields to the CRM is human-approved. They are in open beta on Launch, Growth and Enterprise.

How do you set it up?

1. Connect the CRM with a restricted integration user. CRM integrations are on Growth and above, from $495/mo billed monthly ($446/mo billed annually) (pricing).
2. Build one Function for the write you want, for example "enrich contact, check CRM for duplicate, create lead if net-new".
3. Enable MCP for reps on that Function with an actionable name and description.
4. Invite reps as Sales Reps and set a default credit limit.
5. Watch per-rep usage in the MCP users table and in Settings, then Usage.

FAQ

Can a rep write a field to the CRM that ops did not approve?

Not through MCP: reps can only run Functions an admin enabled, and those Functions define the writes. Users with the Editor role in the Clay app can build workflows, so keep rep accounts on the Sales Rep type if you want writes limited to Functions.

Can ops see what each rep is doing?

MCP spend appears in Settings, then Usage, grouped by Function, and per-user consumption shows in the MCP users table (MCP security).

What does running a Function from Claude cost?

The same as running it in a Clay table. Clay says there is no separate MCP allowance and no MCP surcharge.

Can we restrict which AI tools connect?

Yes. Allowed MCP clients controls which platforms members can connect. Clay cannot verify whether a rep uses a company-managed or personal account on that platform, so enforce that through your AI vendor's admin controls.

Give reps research freedom with Clay

Start with one Function that writes a single object safely, enable it for three SDRs as Sales Reps, and set a modest credit limit. Review the records it creates for a week before widening access.