Skip to content

Module 03 · Lesson 12

Design tools, approvals, and handoffs

Give an agent only the actions and information the job truly needs.

Updated August 2026 · AI Agency Academy

What you will learn

Make a clear, safer operating decision.

You will be able to set least-privilege tool access, approval boundaries, and a handoff that lets a person continue without repeating the customer’s story.

Why this matters

Good agent work is useful before it is impressive.

Most avoidable agent failures come from too much authority, not too little intelligence. The first safe version often reads information, drafts a recommendation, and asks a human to approve the consequential action.

Field note 12

Make the relationship visible.

Core concepts

The language that keeps the work clear.

Least privilegeAccess only to the data and tools required for the job—nothing broader.
Saved on this device.
Reversible actionA change that can be safely undone with a clear record.
Approval gateA human decision required before an agent sends, changes, charges, deletes, or commits a sensitive action.
Handoff packetThe short context a person needs: request, evidence, recommendation, reason, transcript, and next action.
The practical method

Work through the decision in order.

  1. 01

    List every tool

    Write each lookup, write, send, schedule, payment, or deletion capability separately.

  2. 02

    Rank consequences

    Mark which actions are informational, reversible, customer-facing, financial, sensitive, or irreversible.

  3. 03

    Set the first boundary

    Start with read-only or recommend-only when uncertainty or impact is high.

  4. 04

    Build the packet

    Require the agent to preserve the facts, reason, customer request, and recommended next step for the human owner.

Worked example

A realistic, bounded implementation.

An agency builds an appointment assistant for a contractor. It can read service areas, appointment availability, and a lead’s stated needs. It can recommend a slot and create a draft booking record.

It cannot cancel an existing appointment, promise a price, or message a customer outside approved templates without an owner’s approval. If the lead describes a safety risk, it creates an urgent task and uses the approved emergency-routing message.

The dispatcher receives the full handoff packet, not a vague notification that says ‘AI needs help.’

Build it in practice

Use this copyable working template.

Adapt it to the client’s evidence, policy, people, and tools. Do not treat placeholders as approved instructions.

Tool: [name]. Purpose: [why needed]. Access: [read / recommend / act]. Consequence if wrong: [impact]. Approval required: [yes/no + owner]. Handoff fields: [list].
Spacebrain implementation

Put the operating system around the agent.

Use roles, workspace access, approval-oriented tasks, controlled automations, message templates, and CRM timelines to enforce the agreed trust boundary.

Practice

Before you move on

  • Inventory the proposed agent’s tools.
  • Downgrade one risky action to recommendation or approval.
  • Review whether the human can reconstruct what happened from the handoff packet.
  • Every tool has a job-specific purpose.
  • High-impact actions have approval or are removed.
  • The handoff contains evidence and a next step.
  • The first release is more limited than the eventual ambition.

Put the learning to work

Build an AI service people can trust.

Create a free Spacebrain account and use the operating layer around your AI service.

Start free trial