Kyvvu

Policy · high

Bound resource calls per task to prevent runaway loops

Blocks tasks that issue more than 50 step.resource calls.

The policy

A few lines of YAML in your repository.

Part of OWASP agentic default. Assign the pack, or copy this policy into a manifest of your own.

Verdict
High: the step runs, and Kyvvu records a warning and opens an incident.
Checked
Before every step, against everything the agent did earlier in the task.
Rule
execution_max_steps
OWASP agentic
ASI02, ASI08
- name: "Bound resource calls per task to prevent runaway loops"  description: |    ASI08 (Cascading Failures), ASI02 (Tool Misuse - looping pattern):    Blocks tasks that issue more than 50 step.resource calls.    Catches the most common dev-time embarrassment: an agent stuck in    a tool-call loop, which under OWASP's framing is both a DoS/cost    issue and a precursor to cascading failures across connected agents.    50 is generous enough that legitimate multi-step workflows do not    hit it; production deployments typically tighten per-agent based    on observed normal behaviour.    Applies to: ALL agents.  rule_type: execution_max_steps  params:    kind: step.resource    max_steps: 50  severity: high  enforcement_point: step_execution

Why it matters

Catches the most common dev-time embarrassment: an agent stuck in a tool-call loop, which under OWASP's framing is both a DoS/cost issue and a precursor to cascading failures across connected agents.

50 is generous enough that legitimate multi-step workflows do not hit it; production deployments typically tighten per-agent based on observed normal behaviour.

Applies to: ALL agents.

How the rule works

execution_max_steps: Checks that the task has not exceeded a maximum count of the given action kind.

  • kind: step.resource. Action kind to count.
  • max_steps: 50. Maximum number allowed per task.

OWASP agentic threats it addresses

In these packs

From Kyvvu's open policy library at github.com/Kyvvu/manifests, Apache 2.0.

Next

Watch it decide.

In your browser

Try it in the playground

The policy is loaded. Add the steps your agent takes and watch the engine decide, step by step.

On your machine

Five minutes, no account

kyvvu try runs a demo agent against the bundled baseline. Then assign this pack from the dashboard or the CLI.

For security teams

See it on your agents

A 30-minute demo on the agents you actually run, with the policies that fit them.