02 / Agent permissions

Decide what your agents may do.

Set tool permissions, require approval for selected actions, and limit how far a run can go. Orlo records the steps you send it and the decisions it returns.

Try a decision

A decision before the action.

The Orlo workspace

Set permissions for each tool.

In this workspace, looking up an order is allowed, issuing a refund needs approval, and closing an account is blocked.

Rules for Refund assistant agent

5 tool rules. Any tool without a rule is blocked. Each change shows what it would have done to recent calls before you save it.

Tools Limits

Tool Decision Last 7 days

lookup_order Read actions Allowed 806 calls

issue_refund Write actions Needs approval 118 calls

search_knowledge_base Read actions Allowed 2 calls

close_account Delete actions Blocked 1 call

send_customer_email Network actions Allowed with a warning 1 call

A person in the loop

Approve or reject a proposed action.

Orlo checks the proposed action. Your runtime enforces the decision. A person steps in where your rules require one.

Choose a proposed action

The runtime remains responsible for executing tools and enforcing the decision.

Explore an example approval decision.

✓

Set limits for the run.

Set limits on steps, tool calls, and write actions. Give your runtime a clear point to stop.

↳

Require approval before execution.

Require approval for a proposed action. Your runtime waits for that decision before executing it.

Review the rule behind a permission decision.

Review the proposed action, the rule it matched, and the approval decision in the run’s record.

Next / In production

Check live answers against your task’s rules.

Explore production