ASI02: Tool Misuse
Agent invokes high-privilege tools (file delete, payment, code exec) without proper authorization.
Last reviewed July 2026
The gap ASI02 closes
In OWASP Agentic Top 10, Tool Misuse addresses tools. Agent invokes high-privilege tools (file delete, payment, code exec) without proper authorization. Penaxtra records this control at critical severity and establishes its state by exercising it against the running system, so the result reflects observed behavior rather than a documented assertion.
How Penaxtra delivers ASI02
Penaxtra ships adversarial probe families that target tool misuse directly. Each probe runs against the live endpoint on a schedule, and every triggering response is scored by three independent judges and a meta-judge before it is recorded as a finding under the ASI02 identifier. The OWASP Agentic Top 10 ASI02 identifier is attached when the finding is created, so it appears in the exported evidence pack already mapped to the control. Where the same weakness maps to another framework, the finding carries those control identifiers as well.
ASI02 capabilities
Findings tagged with the OWASP Agentic Top 10 ASI02 identifier
Penaxtra severity for this control (critical)
Cross-framework identifiers attached to the same finding where controls overlap
PDF and JSON evidence export with the control identifier attached
ASI02 compliance mapping
Findings for ASI02 carry the OWASP Agentic Top 10 ASI02 identifier along with the corresponding control identifiers in the other frameworks Penaxtra maps, so one result is reflected across each mapped framework.
Frequently asked
What is ASI02 (Tool Misuse)?
Agent invokes high-privilege tools (file delete, payment, code exec) without proper authorization. It is a OWASP Agentic Top 10 control; Penaxtra assesses it at critical severity.
How does Penaxtra test for ASI02?
Penaxtra ships adversarial probe families that target tool misuse directly. Each probe runs against the live endpoint on a schedule, and every triggering response is scored by three independent judges and a meta-judge before it is recorded as a finding under the ASI02 identifier.
Does a finding for ASI02 help with an audit?
Each finding is tagged with the OWASP Agentic Top 10 ASI02 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.