Acceptance criteria
Detect excessive permissions, unexpected tools, destructive operations, abnormal call sequences and policy bypass.
Why it matters
Destructive or unusual agent actions are often the first sign of a hijacked or misconfigured agent.
How to verify
A destructive or out-of-pattern tool call in the pilot is flagged with context.
OWASP adoption context
The listed connected-agent contexts can produce abnormal tool sequences, excessive scope or destructive operations that ordinary prompt inspection may miss.
Framework mappings
Detecting destructive operations, unexpected tools, abnormal call sequences and policy bypass supplies adverse-event analysis and monitoring of agent behavior. Excess-permission findings also inform access-right review; detection does not prevent an operation or reduce its permissions. ISO/IEC 27001: A.8.16: Event assessment and response remain wider dependencies; test false-positive and response handling.
Runtime findings supply the monitoring and evaluation component of post-deployment risk management. A detection capability alone does not establish the wider plan for user input, incident response, recovery and change management.
Destructive calls and excessive permissions expose tool-misuse and identity-abuse patterns; abnormal sequences and policy bypass can also flag rogue-agent behavior. These are indicators for investigation, rather than proof that every anomalous agent is compromised or that the behavior is contained.