Checklist
Bound the total effect of one agent run
A slow mistake can still reach every record. Set a total limit as well as a rate limit, and decide how further actions will stop.
Before you use it
- Use when
- An automated agent can repeat actions quickly or affect many records before a person notices.
Keep this limit in mind
- Rate limits and stop controls reduce blast radius; they do not substitute for correct permissions, validation and approval.
Current editorial reading
Set separate limits
Before a bulk task, name the maximum records, actions or spend allowed for one run. Set the action rate separately. A rate limit restricts actions within a time window; it does not by itself impose a total run budget. Enforce the chosen limits outside the model, alongside normal permissions and approval.
Test the stopping point
For a catalogue update, allow a small named batch and require review before more records can change. In a safe test, try one action beyond the batch limit and verify that it is blocked. Check who can stop further work and what happens to actions already sent. A stop signal does not undo completed changes; document recovery only where it is available.
Take it with you
Before scaling up, verify the total cap, the rate limit and the stop path separately. A bounded run can still perform a harmful action, so keep permission, validation and approval checks in place.
Sources and evidence (2)
What we checked
OWASP describes rate limiting as a damage-limitation measure for agent actions within a time period.
Selected passages read on 2026-10-04. The rate applies over time; the separate total-run cap and boundary test are editorial implementation advice.
LLM06:2025 Excessive Agency · Prevention and Mitigation Strategies; damage-limitation bullets after item 8
NIST AI RMF includes shutdown, modification or human intervention when AI systems depart from expected behavior.
Selected passage read on 2026-10-04. NIST calls for context-specific safety measures, not a universal stopping or rollback mechanism.
AI Risks and Trustworthiness · AI RMF 1.0, section 3.2 Safe, final two paragraphs
OWASP distinguishes damage-limitation measures from controls intended to prevent excessive agency.
Selected passage read on 2026-10-04. A cap or stop path does not replace authorization, input validation or approval. The proposed check is not a measured efficacy claim.
LLM06:2025 Excessive Agency · Prevention and Mitigation Strategies; paragraph introducing logging and rate limiting
Editorial sources (2)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingBound the total effect of one agent run
From this idea
This idea is useful withPut approval immediately before the high-impact actionThis idea is useful with
Monitor the agent after deployment
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaBound every autonomous agent loop before it starts
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
OWASP recommends rate limiting to reduce the number of undesirable agent actions, while NIST safety guidance includes the ability to shut down, modify or intervene in systems that deviate from expected behavior.
A rate cap and stop path limit damage; they do not make an unsafe autonomous action acceptable.
LLM06:2025 Excessive Agency · Damage-limitation controls: rate limiting
All sources (1)
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details