Skip to main content
Batoi AIF Docs

Tools and Bounded Agents

Execute permission-aware tools within explicit step, duration, review, and idempotency controls.

Version Foundation release Early foundation work Reviewed Jul 21, 2026 Next review Sep 21, 2026
Start Reading Open AIF GitHub Report documentation issue

Owner: Batoi Engineering Reviewed by: Batoi AIF Maintainers Source revision: cd680e8

Start SafelyEvaluate AIF and learn the development and governed runtime boundary. Human ReviewPause operations before side effects and resume with replay-protected approval. Governed RAGApply workspace and ACL filters before ranking and retain citation evidence. RAD IntegrationUse the included PDO persistence, review, policy, queue, and context adapters.
AIF is the public engineering framework. For the managed intelligence capability used across supported Platform and Flex workflows, see Batoi Intelligence.
Browse Batoi AIF Documentation Tools and Bounded Agents
On this page

Tools and Bounded Agents

AIF tools are backend capabilities executed through the governed gateway. They are not unrestricted model functions.

Tool Definitions

A tool definition declares:

  • stable tool code and description
  • required arguments
  • required permissions
  • side-effect classification
  • whether human review is required
  • idempotency behavior

The gateway checks permissions and policy before invoking the tool. Non-idempotent side-effecting tools require an idempotency key.

Bounded Agent Runner

BoundedAgentRunner executes an explicit list of registered tool calls through AifGateway. AgentBudget limits the number of steps and total duration. Exceeding either boundary stops the run with AgentBudgetExceededException.

The runner does not permit autonomous bypass of policy, review, tool registration, or audit logging.

Safe Integration Pattern

  • Register only server-owned ToolInterface implementations.
  • Resolve the caller through a trusted ExecutionContext.
  • Keep provider credentials and tool secrets outside model-visible arguments.
  • Require review for meaningful external side effects.
  • Use stable idempotency keys for retryable mutations.
  • Audit every terminal outcome.