Pular para o conteúdo principal

Review MCP traffic logs

Implementation Effort: Low

User Impact: Low

Overview​

Zero Trust requires continuous visibility into how AI agents communicate with the tools and resources they use. As agents increasingly rely on the Model Context Protocol (MCP) to reach remote MCP servers, organizations need to know which servers are in use, what tools and resources they expose, and how those tools are invoked. Global Secure Access MCP traffic logging uses deep packet inspection to identify MCP traffic by the protocol itself—rather than a predefined cloud app catalog—so it can surface previously unknown, private, and shadow MCP servers and help you enforce stronger governance over agent communications.

Reviewing MCP traffic logs follows these key steps. See the linked documentation for detailed implementation instructions.

  1. Confirm prerequisites — Ensure you have a Global Secure Access license and the Global Secure Access Administrator or Log Reader role. For end-user devices, the Global Secure Access client must be installed with Internet Access traffic forwarding and TLS inspection enabled (MCP data is in the encrypted payload). For Copilot Studio agents, enabling the Global Secure Access integration logs MCP traffic without requiring TLS inspection. Only traffic to remote MCP servers is captured.
  2. View MCP traffic logs — In the Microsoft Entra admin center, browse to Global Secure Access > Monitor > Generative AI Insights, then set the Activity filter to MCP to see only MCP traffic events.
  3. Inspect event details — Select any log entry to open the details pane and view the full MCP payload, including the sub-activity type (such as initialize, tools/list, or tools/call), the request or response content, and server-reported tool descriptions and capabilities in initialize responses. Use the Event ID to match a request with its response and the Transaction ID to correlate with network-level traffic logs.
  4. Filter and sort — Narrow the view by Sub-activity (for example, tools/call to focus on tool invocations), Destination URL, or User to understand which servers and tools are being used, and export the filtered results for offline analysis.
  5. Discover MCP servers — Review unique values in the Destination URL column (the reliable identifier for an MCP server) to identify shadow or unknown servers, select an initialize response to review advertised tools and capabilities, and use URL filtering to block traffic to any risky server.

Reference​