How to meet it
OWASP AISVS v1.01
Orchestration & Agentic Security · Execution Budgets, Loop Control, and Circuit Breakers
Quotas and timeouts for every tool
Verify that per-tool quotas and timeouts (e.g., CPU, memory, disk, egress, and execution time) are enforced by the runtime.
OWASP AISVS v1.01, requirement 9.1.1
In plain English
Give every tool hard limits on CPU, memory, disk, network traffic and run time, enforced by the platform it runs on. A tool that loops or is abused then stops at a known ceiling.
What good looks like
- Each tool has documented limits for compute, memory, disk, egress and duration.
- The runtime enforces them, so the tool's own code cannot raise them.
- Hitting a limit ends the call and is logged.
How teams usually do it
- Container resource limits and timeouts for each tool process.
- Egress quotas or proxies for tools that reach the network.
Evidence an auditor would accept
- Tool runtime configuration showing the limits.
- A test where a tool exceeds a limit and is stopped.
Common mistakes
- Timeouts set in the agent's prompt or code instead of the runtime.
- No egress limit, so a compromised tool can send out data freely.
Not sure which requirements apply to your system? Take the assessment.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.