c4.8 Log tool invocations with user attribution and observability
Record who invoked which tool, with what parameters, and trace tool chains, so tool misuse and anomalous behavior are detectable and auditable.
Implementation guidance
How to implement on AWS
Enable CloudTrail (organization trail) to log tool invocations with user-context attribution and forward to the Log Archive account. Monitor invocation rates, duration, and failures with CloudWatch alarms. Use AgentCore Observability to trace tool chains and multi-agent workflows; for OS tools, log via Systems Manager Session Manager.
Acceptance criteria
Tool invocations are logged with user attribution and centralized; CloudWatch alarms on anomalous tool metrics; tool-chain traces are available.
Practical implementation
How this control is implemented in each reference architecture:
Tool invocations are logged with user attribution via the org CloudTrail to the Log archive, AgentCore Observability traces tool chains, and CloudWatch alarms on anomalies.
- Enable the organization CloudTrail to log tool invocations with user-context attribution and forward to the Log archive account.
- Use AgentCore Observability to trace tool chains and multi-agent workflows; for OS-level tools log via Systems Manager Session Manager.
- Alarm in CloudWatch on invocation rate, duration, and failure anomalies for tools.
How to validate: Tool invocations are logged with user attribution and centralized in the Log archive; CloudWatch alarms on anomalous tool metrics; tool-chain traces are available.
Avoid: Logging that a tool ran but not who triggered it or with what parameters. Without user attribution you cannot investigate tool misuse.
In-account CloudTrail with user attribution, AgentCore Observability tracing, and CloudWatch anomaly alarms make tool misuse detectable and auditable.
- Log tool invocations with user-context attribution via CloudTrail into the in-account Object-Lock log bucket.
- Trace tool chains with AgentCore Observability; log OS-level tools via Systems Manager Session Manager.
- Alarm on anomalous tool invocation rate, duration, and failures in CloudWatch.
How to validate: Tool invocations are logged with user attribution; CloudWatch alarms on anomalous tool metrics; tool-chain traces are available.
Avoid: No trace across a multi-step tool chain. Capture the chain so an anomalous sequence of tool calls can be reconstructed.
Threats addressed
- Tool misuse or anomalous invocation patterns going undetected.
- No audit trail attributing a tool action to a user.
AWS services
Framework mappings
OWASP GenAI/LLM Top 10 (2026)
- LLM03 Excessive Agency
- LLM06 Unbounded Consumption
NIST AI Risk Management Framework (AI 100-1)
- MEASURE.3 Mechanisms for tracking AI risks are in place
- MANAGE.4 Risk treatments, monitoring and response are documented and applied
AWS Security Hub — AI Security Best Practices
- BedrockAgentCore.6 Bedrock AgentCore custom browsers should have session recording enabled
AWS Well-Architected Generative AI Lens (Security)
- GENSEC03-BP01 Implement control plane and data access monitoring
OWASP GenAI Top 10 for Agentic Applications (2025)
- ASI08 Cascading Failures
Learning resources
References
- AWS SRA for AI — Capability 4, Logging and monitoring
AI Security Maturity Model