Keep people in control
Let routine calls through, pause the rest
Keep approvers for the calls that need judgment instead of every call to a tool.
Attach one condition to a gated tool - a refund under 200, say - and calls that meet it run without waiting.
What this changes for your team.
Under each tool an agent gates, its author may name one argument of the call, a comparison and a value. A call that meets the condition runs without pausing; a call that misses it, or whose argument is missing or not a number, pauses as usual. The rule checks only the argument it names and ignores the call's others, and it checks a list only at the position named - a rule on an email's first recipient does not look at the other recipients, cc or bcc, so where those matter the pause should stay. The rule can only ever remove a pause the author added: a tool the organization requires approval for pauses whatever the rule says.
How it works in practice.
- 01
Gate the tool in the agent's Approvals settings.
- 02
Tick Skip the pause when a condition holds, and name the argument, the comparison and the value.
- 03
Publish; the rule is part of the setup and shows in the publish diff.
What you can plan around.
What to expect, including limits that matter to your team.
One rule per tool - an argument path, one of five comparisons and a literal - so a reviewer can read it in a line.
Every skipped pause is recorded in the audit log and on the call itself.
The condition is never consulted for an organization-required tool.
Bring one real process
See how Yekar.AI fits the way you work.
Start with a job your team already owns, plus the tools and decisions around it.
Get started