# Bound how much damage one agent run can do

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Bound how much damage one agent run can do

ID: MHC-D-RESEARCH-0322 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/bound-how-much-damage-one-agent-run-can-do

Automation turns one mistake into throughput unless you design a brake.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- An automated agent can repeat actions quickly or affect many records before a person notices.

### Avoid when

- Rate limits and stop controls reduce blast radius; they do not substitute for correct permissions, validation and approval.

### Explanation

Set limits on action count, affected resources, spend or batch size that match the task. Add a visible stop path for behavior outside expectations and make recovery possible where the downstream system supports rollback. The aim is not to make bad actions acceptable; it is to prevent one error from scaling silently.

### Checklist

- One run has an explicit maximum action or resource scope.
- Unusual action rates can be detected or stopped.
- A human can halt or suspend further actions.
- High-impact batches are split or sampled before full execution when practical.
- Rollback or compensating action is documented where available.

### Example

An agent updating customer records first changes a small bounded batch and pauses on error-rate thresholds instead of editing the full database in one pass.

### Check

You can state the maximum plausible effect of one unreviewed run under the configured controls.

### Limits

- Rate limits and stop controls reduce blast radius; they do not substitute for correct permissions, validation and approval.

### Evidence and sources

- supports: 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. — RS-EEEBBCF69A614717. A rate cap and stop path limit damage; they do not make an unsafe autonomous action acceptable. (Damage-limitation controls: rate limiting)
- RS-EEEBBCF69A614717: LLM06:2025 Excessive Agency — https://genai.owasp.org/llmrisk/llm062025-excessive-agency/

### Vedokrok editorial review

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.

#### 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.

**Editorial takeaway:** 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.

#### Editorial evidence

- supports: OWASP describes rate limiting as a damage-limitation measure for agent actions within a time period. — RS-EEEBBCF69A614717. Selected passages read on 2026-10-04. The rate applies over time; the separate total-run cap and boundary test are editorial implementation advice. (Prevention and Mitigation Strategies; damage-limitation bullets after item 8)
- supports: NIST AI RMF includes shutdown, modification or human intervention when AI systems depart from expected behavior. — RS-37C3116E2E2D73CF. Selected passage read on 2026-10-04. NIST calls for context-specific safety measures, not a universal stopping or rollback mechanism. (AI RMF 1.0, section 3.2 Safe, final two paragraphs)
- limits: OWASP distinguishes damage-limitation measures from controls intended to prevent excessive agency. — RS-EEEBBCF69A614717. 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. (Prevention and Mitigation Strategies; paragraph introducing logging and rate limiting)
- RS-EEEBBCF69A614717: LLM06:2025 Excessive Agency — https://genai.owasp.org/llmrisk/llm062025-excessive-agency/
- RS-37C3116E2E2D73CF: AI Risks and Trustworthiness — https://airc.nist.gov/airmf-resources/airmf/3-sec-characteristics/

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/put-approval-immediately-before-the-high-impact-action
Related (useful_with): https://vedokrok.com/knowledge/monitor-the-agent-after-deployment
