Skip to content

Human approval for AI agent actions, with an audit trail

Human approval for AI agent actions in SaaS apps: client prompts, role restrictions, access requests, workflow approvals and one audit trail.

Roopendra Talekar Updated 9 min read
A sales role with the opportunity update and email send tools restricted, beside an approval card and the audit trail that records each AI agent action

Tools that let AI agents take actions in SaaS apps with approvals and an audit trail include Elaichi, Glean, and the approval settings inside Claude and ChatGPT. Elaichi lets Claude, ChatGPT, Cursor or any MCP client act in 650+ connectors, keeps risky writes behind a decision someone else makes, and records every call in one audit log.

How do you get human approval for AI agent actions like CRM writes and email?

Human approval for AI agent actions comes in two kinds. The first is a prompt in the AI client, answered by the person who asked. The second is a decision an admin makes ahead of time about which roles may run the write at all. Elaichi handles the second kind, and its audit log records how each call was approved.

A RevOps lead sees the request coming. Reps want Claude to update close dates in Salesforce and to send follow-up email from Gmail. The lead wants a person to sign off before either happens. Security wants the same thing, written down somewhere an auditor can read.

MCP (Model Context Protocol) is the standard way an AI assistant calls tools in other apps. Elaichi serves every connected app through one organization endpoint, the single address each client signs in to. Claude, ChatGPT, Cursor, Microsoft Copilot and any other MCP client all use it. The MCP specification asks for a human in the loop who can deny a tool call. It also says servers must implement proper access controls. Approval needs both halves, and they live in different places. Over MCP, the person's OAuth grant is the approval, so Elaichi does not ask before each call.

Which tools let AI agents act in SaaS apps with approvals and an audit trail?

Three kinds of tool do it, and each one approves at a different moment. AI clients ask the person at the moment of the call. Claude's connector tools can be set to Needs approval (Claude Help Center, checked October 2026), and ChatGPT may show an approval card before a write (OpenAI Help Center, checked October 2026). Glean describes "human-in-the-loop controls that let you require approval before execution" for the actions its agents take (Glean connectors, checked October 2026).

Elaichi puts an admin's decision in front of every client at once. A restriction takes a write away from a role, and an access request lets someone else open it for one person. On the Black plan, a workflow's approve step waits until a named person approves, in the console or in Slack. Only a person can answer, never the AI. Every call that reaches execution is written to one audit log, with how it was approved. A side-by-side read of who signs off and what each platform records sets these three kinds against one another.

How do you let employees use AI on company tools but require approval for risky actions?

Let reads and drafts run freely, and put each risky write behind a decision somebody else makes. In Elaichi that takes three settings, and each one applies to Claude, ChatGPT, Cursor and every other client at once.

  1. Restrict the risky tools on each role: sends, deletes and record updates. A restricted tool is left out of the tools Elaichi offers a client and cannot be called. Search still names it, flagged restricted, with no schema.
  2. Let members file an access request when they need one of those tools. Someone with member:manage decides it, and never the person who asked.
  3. On the Black plan, move repeat writes into a workflow with an approve step, so a named person signs off before the step runs.

Everyday questions keep running with no prompt, so employees still get quick answers from their apps.

What actions should an AI agent be allowed to run without human approval?

Let an agent run reads and drafts on its own. Put sends, record updates and deletes behind a person or a restriction. In the Elaichi Agent, which comes with the Black plan, a read runs without a card, a write shows an approval card unless the person chose Always allow, and a delete asks every time. From an MCP client, the sign-in grant is the approval, so restrict the risky tools by role.

A thread on r/AI_Agents asks where to draw this line. The draft is a useful dividing point. The agent writes an email into Gmail, and the rep reads it and presses send. While the send tools are restricted on the role, the agent cannot skip that step.

Restrict the send tools by name, including gmail_drafts_send, which the console labels Read only. For a write that must stay, freeze the fields that pick the destination, so the agent cannot choose them.

What does an approval prompt in Claude, ChatGPT or Cursor check?

It checks with the person in front of the client, at the moment of the call. That is useful, and it is not a second pair of eyes. The approver is the same person who asked for the action.

Each client handles it differently (all checked October 2026):

  • Claude. Each connector has tool permissions set to Always allow, Needs approval or Blocked, per tool or per group (Claude Help Center). On Team and Enterprise plans, owners can restrict a connector's tool actions for the whole company, and members cannot override that.
  • ChatGPT. For a write, ChatGPT may ask for confirmation, depending on the app's permissions and the context. Some risky actions are refused rather than offered for approval (OpenAI Help Center).
  • Cursor. "Cursor asks for approval before using MCP tools by default" (Cursor docs). In its Auto-review mode, allowlisted tools run without asking, and Enterprise admins can limit which tools may run automatically.

There is one catch with Elaichi behind any of them. In Elaichi, connected tools are never listed one by one, however few there are. The model finds a tool with search_tools and runs it with execute_tool. A client permission therefore names execute_tool, so one setting covers a Salesforce read and a Gmail send alike. The real tool name sits inside the call's arguments.

A client prompt suits a careful person double-checking their own request. It is not a second person's decision on that call.

Does the Elaichi Agent ask before it writes?

Yes. In the Elaichi Agent, a write stops at an approval card before it runs. The card offers Deny, Allow once and Always allow. The person can also edit the arguments first, and the button then reads "Save & allow once".

Deletes get stricter treatment. Always allow is offered for writes only, so a delete asks every time. Always allow is remembered per person and per operation.

Calls from Claude, ChatGPT or Cursor take a different route. Over MCP, Elaichi cannot put an approval step in the client's own window. So the approval is the OAuth grant (the permission a person gives a client at sign-in). On Elaichi's consent screen, the person ticks what the client may do. "Make changes" covers writes, and "Delete things" is never ticked in advance. Without the write box, a client cannot change Elaichi's own records. A connected app's create, update and delete tools all ride on "Use your connected apps"; the delete box covers only Elaichi's own deletes. Holding a connected app to reads is a restriction on the role, not a consent checkbox.

Both routes still ask the person who started the request. The layers below are the ones an admin holds.

How do you take a write away from a role?

Write a restriction. A restriction decides which connectors and which individual tools a target may reach. In Elaichi, restriction targets are role or user only; the organization default is the absence of a rule, which means allow everything. Restrict the write on the Sales role, and no rep's client is offered it again.

For a sales team, the rule names four tools. update_a_salesforce_opportunity_by_id changes close dates, stages and amounts. create_a_gmail_message sends a message straight away, and gmail_drafts_send sends a saved draft. create_a_gmail_batch groups Gmail requests, including sends, into one call. Reads stay, and so does create_a_gmail_draft. The four things an agent needs before it changes a record sets out that write path in order.

That is the answer to read but not delete or send. Restrict the send and delete tools by name, and keep the reads. A restricted tool is left out of the tools Elaichi offers a client and cannot be called. Search still names it, flagged restricted, with no schema. A block always beats an allow.

Here, the draft is where the human approval happens. The agent writes the email into Gmail. The rep reads it there and presses send. While the send tools are restricted, the agent cannot send. It can only save a draft. No setting in a client can skip that step.

This follows OWASP's guidance on excessive agency. It advises putting authorization in the downstream system, not in the model's judgment. Its mailbox example makes the same cut: read, do not send. A saved restriction reaches every surface within about two minutes. Restricting one tool or the whole app covers when to name tools and when to name the connector.

Can you narrow a write instead of removing it?

Yes, with frozen parameters. A frozen parameter is a value an admin fixes on one tool inside a toolbox, a saved set of tools paired with connected accounts. Elaichi removes the field from the schema the model sees. It then writes the frozen value over the call's arguments, so sending the field anyway changes nothing.

Take a support team that hands leads to sales and holds no Salesforce login. RevOps connects its own Salesforce account and keeps that connection unshared. It pins create_a_salesforce_task into a toolbox and freezes the owner field to the deal desk's Salesforce user, using the field name from the tool's schema. It then shares the toolbox with the support team at use. Every task the support team's agent creates lands with the deal desk. The write itself becomes the request for a person to look.

A template carries the same tool list, with renames, defaults and frozen values, and no account. In Elaichi, a freeze binds only calls made through its toolbox entry, so share the toolbox with the people it governs, not the connection itself. A rep with their own Salesforce connection reaches the same tool unfrozen. Locking a tool argument works the payment version through.

What happens when someone needs a restricted tool?

They file an access request, and someone else decides it. Any member can file one with no permission needed. Resolving it needs member:manage, which People Admin, Org Admin and Org Owner hold. An admin cannot decide their own request.

Approving a request caused by a restriction creates an access grant for that one requester. A rep restricted through the Sales role has that one tool lifted out of their role rules, so the role's other rules still bind them and nobody else changes. No rule is written and the role is not edited. Like any restriction change, it reaches every surface within about two minutes.

Two limits keep this honest. First, no access request can be approved or denied from the Elaichi Agent or an MCP client. Restrictions stay read-only on every AI surface, so a model cannot approve its own access. Second, an approval is a standing grant, not approval of one call. It lasts until the member is removed or an admin approves a replacement.

What does the audit log show after the fact?

Every call that reaches execution, and how it got past the approval step. The audit log is the record Elaichi keeps of each action. It holds one entry for each connected-tool call that reaches execution (a call refused earlier writes none), naming the person, the client and the account reached.

Each tool call states its approval in plain words:

Route What the audit log says
A read Didn't need approval because it only read data
Elaichi Agent card Approved by the person, in chat
Edited arguments Edited by the person before it ran
Remembered choice Allowed automatically by an "always allow" choice
Claude, ChatGPT or Cursor Allowed by the access that client was granted

Elaichi logs the one path argument that names the object, as the target id, and nothing else about the arguments. So the log shows that an opportunity update ran, through which account. It does not show the new close date. Give the reviewer an Auditor seat, which is read-only, cannot call tools and costs no license. What an AI audit log must capture covers the full record.

How does the setup look for a sales team?

Two roles, four restricted tools and one review habit. Each member holds exactly one role, so a role describes a whole job. Custom roles are a Gold feature.

Role Read Salesforce Draft email Update opportunities Send email
Sales (custom) Yes Yes Restricted Restricted
Sales Ops (custom) Yes Yes Yes Yes
A rep with an approved request Yes Yes Opened for them Restricted

Set it up in this order:

  1. Create both as custom roles carrying Member's permissions, including tool:execute.
  2. Restrict update_a_salesforce_opportunity_by_id, create_a_gmail_message, gmail_drafts_send and create_a_gmail_batch on the Sales role.
  3. Have each rep connect Salesforce and Gmail under their own login. Each rep's own Salesforce permissions then apply to what they reach.
  4. Wait about two minutes. Then, as a test rep, search for a restricted tool and confirm it comes back only by name, flagged restricted.
  5. Each month, filter the audit log by the Salesforce connection and read the writes.

The same shape answers how to give sales, engineering and HR different AI tool access. Give engineering and HR their own roles and restrict the Salesforce connector for both. The CRM then cannot be reached from their clients. Designing roles for AI agents covers the role chain. For the full Salesforce tool list a sales role should lose, see the sales team playbook.

When is a client prompt enough?

When one team uses one client, and the source app already says no. A Claude Team owner can restrict a connector's tools for the whole company in Claude's own settings. If reps hold a read-only Salesforce profile, the write fails at Salesforce too. A restriction layer on top would add review work and little safety.

The admin layers earn their cost later. That point comes when more than one client reaches more than one app, and a reviewer asks who approved last Tuesday's change. The MCP control plane overview explains where Elaichi sits. The risks these layers answer are listed in the MCP security risks guide, and pricing has the price for your region.

FAQ

Frequently asked questions

Which tools let AI agents take actions in SaaS apps with approvals and an audit trail?

AI clients such as Claude and ChatGPT can ask the person using them before a tool runs. Elaichi adds the decisions an admin makes for every client at once: restrictions that take a write away from a role, access requests that someone else approves, and, on the Black plan, workflow approve steps that wait for a named person. Each call that reaches execution is written to one audit log, with how it was approved.

Can an admin approve AI agent actions before they run?

In Claude, ChatGPT and Cursor, an approval prompt goes to the person using the client, who is usually the person who asked for the action. In Elaichi, an admin decides ahead of time instead. A restriction takes a tool away from a role, and a member who needs it files an access request that someone with the member:manage permission approves or denies. Each call that reaches execution is then recorded in the audit log with how it was approved.

How do I let an AI agent read the CRM but not send email?

In Elaichi, write a restriction on the role that withholds the send tools, which for Gmail are create_a_gmail_message, gmail_drafts_send and create_a_gmail_batch, and leave the read and draft tools alone. A restricted tool is left out of the tools Elaichi offers a client and cannot be called. Search still names it, flagged restricted, with no schema. The person then reviews each draft in Gmail and sends it by hand.

Does a Needs approval setting in Claude work per tool through Elaichi?

Not per connected tool. Elaichi serves connected tools through two tools, search_tools and execute_tool, so a Claude tool permission on execute_tool covers every connected tool at once. Use the client setting as a prompt for the person in the chat, and use an Elaichi restriction on the role to decide which tools that role can reach at all.

Who can approve an access request in Elaichi?

Anyone whose role holds the member:manage permission, such as a People Admin, Org Admin or Org Owner, and never the person who filed it. Any member can file a request. Approving a request creates an access grant for that requester only, and lifts exactly the approved tool or connector out of their role rules. No access request can be approved or denied from the Elaichi Agent or an MCP client.

How do you give sales, engineering and HR different AI tool access?

In Elaichi, give each department its own role and write restrictions for each role. Each member holds exactly one role, so a rule on the Sales role reaches every rep and nobody else. Custom roles are a Gold feature. A role or restriction change reaches every surface within about two minutes.

Put AI to work in your own apps

14 days of Black, no credit card. Start with one app and one team.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot