Policy · critical
Tool calls must be in the declared allowlist
Pairs with registration policy. At runtime, blocks tool calls whose step_name is not in the agent's declared_tools allowlist.
The policy
A few lines of YAML in your repository.
Part of OWASP agentic default and Internal AI starter. Assign the pack, or copy this policy into a manifest of your own.
- Verdict
- Critical: the step is blocked before it runs, and an incident is opened.
- Checked
- Before every step, against everything the agent did earlier in the task.
- Rule
- step_name_in_allowlist
- OWASP agentic
- ASI02, ASI04
- name: "Tool calls must be in the declared allowlist" description: | ASI02 (Tool Misuse), ASI04 (Supply Chain): Pairs with registration policy. At runtime, blocks tool calls whose step_name is not in the agent's declared_tools allowlist. Catches typosquatting, supply-chain swap-ins, and silent capability creep as the agent's prompt evolves. Applies to: ALL agents. rule_type: step_name_in_allowlist params: agent_field: declared_tools target_kinds: ["step.resource", "step.exec", "step.credential"] severity: critical enforcement_point: step_executionWhy it matters
Catches typosquatting, supply-chain swap-ins, and silent capability creep as the agent's prompt evolves.
Applies to: ALL agents.
How the rule works
step_name_in_allowlist: Checks that the step's name is in the agent's declared tool allowlist. Fails closed: with the allowlist absent or empty, every targeted step is blocked.
agent_field:declared_tools. Agent field holding the tool allowlist (e.g. declared_tools).target_kinds:["step.resource","step.exec","step.credential"]. Action kinds the rule applies to (e.g. step.resource, step.exec, step.message); other steps pass.
OWASP agentic threats it addresses
In these packs
- OWASP agentic default, version 1.0.2
- Internal AI starter, version 1.0.2
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.