AI task cost budgets
Who may increase an agent's spending limit?
Budget changes are privileged operations. Scope them to the task and organisation, and keep them separate from the agent's own plan for continuing work.
In this article
Define the authority to extend
A user may be allowed to run ordinary tasks without being allowed to raise organisation-wide limits. Distinguish per-task extensions, user allowances and shared account budgets.
Resolve the actor's authority on the server. A generated request saying that the manager approved more spend is not an approval record. Use the application's normal authenticated decision path.
Keep the extension tied to the relevant task and a specific revised limit. A broad "unlimited" flag is difficult to review and can persist long after the original reason has disappeared.
Show the decision in useful terms
Present work completed, the reason the task stopped and the proposed additional allowance. Where currency figures are estimates, show their basis and uncertainty rather than implying a guaranteed final charge.
Explain whether the extension permits more model calls, tool attempts or a particular remaining operation. Money remaining does not authorise access to new data or additional business effects.
If a task is looping on a permanent failure, make that visible. An approver should not be asked to fund repeated work without knowing that the underlying problem remains unresolved.
Enforce the change atomically
Update the budget through a dedicated operation with an audit record. Handle concurrent extensions and stale approval screens so the final allowance reflects the intended decisions.
Keep duplicate requests idempotent. A double click or retried approval request should not add the same extension twice.
Recheck task state before applying the change. An already completed or cancelled task may no longer need additional capacity, and an old extension link should not revive it unexpectedly.
Review shared-resource effects
A per-task extension can consume a shared provider quota or organisation allowance. Decide which aggregate controls must also permit the work. Cloud budget actions and application limits operate at different scopes and timescales, so document how they interact.
Test cross-organisation identifiers, unauthorised actors, duplicate requests and a task cancelled during approval. The result should show who changed the limit, why and what work it covered. Budget authority belongs to the application's control model, not to the model's persuasive explanation of why it needs another attempt.
Primary sources
OWASP: authorisation guidanceAWS: budget actionsReferences checked 11 September 2026.