# Give the Agent a Budget, Not a Token — Sachin Malhotra, Anthropic

Source: [AI Engineer](https://www.youtube.com/watch?v=rbjWzZK2LU0)  
Feed7 permalink: https://feed7.dev/p/give-the-agent-a-budget-not-a-token-sachin-malhotra-anth-b53948be9f  
Published: 2026-08-22T00:00:00.000Z  
Trust: Source Linked (source_linked)

## Why Included

Bound write volume, rate, reversibility, and visibility, with human-only overrides outside the agent session.

## Source Summary

Production agents need bounded write authority, infrastructure-stamped identity, and human-only overrides; a broad token and tool list cannot control blast radius.

## Practical Implication

Classify write verbs by how failures surface, rate-limit every write, and keep overrides outside agent sessions. Record aggregate behavior with trip wires, size limits using an undo test, and let a trusted proxy stamp agent and session identity.

## Agent-Ready Context

A cleanup agent’s empty pipeline stage removed its filter, matching and deleting about **200 workloads** used by **20 engineers** in **90 seconds**. The proposed alternative treats authority as budgets across action volume, rate, reversibility, and visibility.

Classify write verbs by how failures surface, rate-limit every write, and keep overrides outside agent sessions. Record aggregate behavior with trip wires, size limits using an undo test, and let a trusted proxy stamp agent and session identity.

These are production safety primitives, not a guarantee against bad actions. Limits still need tuning by resource and namespace, while quiet or irreversible operations may require a separate human-held credential.

## Context Map

- Layer: agent
- Domains: coding, security
- Topics: harness-engineering, tool-use, sandboxing

## Uncertainty

- None recorded.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.