OperatorsApprove what agents can do

Updated 27 Oct 2026View as Markdown

Approve what agents can do

Decides which write operations agents can call, approves or withdraws each one once, and has a person decide single actions in Slack.

See it running: Help widget

MCP serverSDK and APIYour own cloud:AWSGCPAzureor hosted by MindsetMindset platformAgentScriptVersionRunConnectionOperationFunctionWidgetSecurity and complianceone posture · audit trail · personal data redactionBuilderscoding agentOperatorsAI clientor the StudioYour appthe SDKYour serverthe APIThe Huband schedulesBuilderscoding agentOperatorsAI client or the StudioMCP serverYour own cloud:AWSGCPAzureor hosted by MindsetMindset platformAgentScriptFunctionConnectionOperationWidgetVersionRunSecurity and complianceone posture for the org,audit trail and personal data redactionSDK and APIYour appthe SDKYour serverthe APIThe Huband schedules

Ask your AI client#

List every write operation the invoice exceptions agent can call in Production, and any that are still waiting for a person's approval.

What you get back#

Each write operation, the connection it's on, and whether it's enabled or pending. Your AI client can't approve a write: no agent can, whichever route it comes in by. A person does that in the Studio. How consent works is on Security and approval.

How approval works#

A write needs consent once per operation, never per call. The org setting Turn on connections that change other systems automatically is on by default, so a new write operation can be called as soon as it's added.

If an operation's definition changes after you approved it, the approval stops applying and you approve the new shape.

ButtonOnWhat it does
Approve this operationA write that Needs your approvalLets agents call it. Recorded with your name
Withdraw approvalAn enabled writeStops every agent and function calling it. It goes back to Needs your approval and stays there, whatever the org setting says
DisableAn enabled readStops every agent and function calling it
DisableA whole connectionRefuses every call to any of its operations

Each takes effect on the next call, with no new version. To stop something right now, this is the fastest way.

Decide one action during a run#

When a person must decide a specific action, the script holds an $ask step. It posts one message to Slack with buttons, and the run waits for the answer or a timeout. See Make it follow steps, and Post to Slack or send email to set up the Slack app.

  • Put it late. Gather, compare and assess first, then ask before the query is registered.
  • Ask once for the batch. One message with every disputed line gets read. Fifty get waved through.
  • Put enough in it to judge: the invoice, the PO, each line that differs and the contract clause.
  • Expect a slow answer. Don't build anything that goes stale in ten minutes.

What you decide#

  • Whether new writes turn on automatically, and who approves them if not. Finance approves finance writes.
  • Which actions need a person each time, as an $ask in the script.

Done when#

  • You can say, for every write the agent uses, whether the org setting or a named person granted it.
  • You know which button stops a write, which stops a read, and which stops a whole connection.

In the Studio#

The setting is on Settings → Systems → Connections that change other systems. A pending write shows Needs your approval on the connection's Operations tab (Tools for an MCP server). Open it to read The exact call and the Parameters the agent supplies, then press Approve this operation. Disable for a whole connection is on its Overview tab.