> ## Documentation Index > Fetch the complete documentation index at: https://docs.box.com/llms.txt > Use this file to discover all available pages before exploring further. # MCP Platform Activity Report
The MCP Platform Activity report is a per-event audit trail of work that third-party MCP integrations perform in Box. Use it to see which files and folders an integration accessed or changed, and which users ran those actions. The report also includes Box AI requests made through an integration. The [MCP Tool Calls Report](/en/box-admin-tools/reporting-and-insights/mcp-tool-calls-report) counts tool calls per day and does not list the content those calls touched. The [Platform Activity Report](/en/box-admin-tools/reporting-and-insights/platform-activity-report) measures API consumption, storage, and bandwidth. ## Run the report 1. Open the **Admin Console**. 2. In the left sidebar, select **Reports**. 3. Select **Create Report**. 4. Select **MCP Platform Activity Report**. 5. Set a date range. Optionally filter by users or groups, and by integrations. 6. Select **Run**. Box writes the CSV to a timestamped folder in **Box Reports** and notifies you when the report is ready. See [Running Reports](/en/box-admin-tools/reporting-and-insights/running-reports) for the shared report workflow. ## MCP Platform Activity report details * **File format**: comma-separated value (.csv) file * **Filename**: `mcp_platform_activity.csv` * **Folder name format**: `MCP Platform Activity Report {date_range} run on {timestamp}` * **Filename and folder name time zone**: Pacific Time (PT) ## MCP Platform Activity report filters ### Date Range Required. Select one of these presets, or a custom start and end date with no maximum range: * Last 30 days * Last 60 days * Last 90 days * Custom range ### Users or Groups Optional. Select managed users or groups. If you leave this field empty, the report includes all users. ### Integrations Optional. Select one or more third-party MCP integrations enabled for your enterprise. If you leave this field empty, the report includes all of those integrations. The list includes only third-party MCP integrations. Box-internal services are not listed. ## MCP Platform Activity report data columns Empty cells mean that column does not apply to the action. ### Always populated columns | Column | Description | | - | - | | Timestamp | When the event occurred | | Integration ID | Unique identifier of the integration | | Integration Name | Name of the integration | | User Name | Name of the user the action ran as | | User Email | Email address of that user | | Event Type | Box admin event for the action, such as UPLOAD, DOWNLOAD, or BOX\_AI\_USER\_REQUEST | ### File context columns These columns populate for file and folder activity. For Box AI requests against a hub, **File Name**, **File ID**, and **Item Type** contain the hub name, hub ID, and the type `hubs`. **File Path**, **File Size**, and **Version ID** populate for: * `create_folder`, `upload_file`, `upload_file_version` * `get_file_content`, `get_download_url`, `get_file_preview` * `update_file_properties`, `update_folder_properties` * `copy_file`, `copy_folder`, `move_file`, `move_folder` * `create_file_comment` * `set_file_metadata`, `set_folder_metadata` `get_file_preview` populates these columns only for renderable formats such as PDF and PPTX. | Column | Populated for | | - | - | | File Name | File, folder, and hub activity | | File ID | File, folder, and hub activity | | Item Type | File, folder, and hub activity (`file`, `folder`, or `hubs`) | | File Path | The MCP tools listed above | | File Size | The MCP tools listed above | | Version ID | The MCP tools listed above | | Parent Folder | File and folder activity | | File Owner | File and folder activity | ### Shared link context columns | Column | Populated for | | - | - | | Shared Link ID | `add_file_shared_link`, `add_folder_shared_link` | ### AI context columns A multi-file Box AI request records one row per file. | Column | Populated for | | - | - | | AI Request ID | `ai_qa_single_file`, `ai_qa_multi_file`, `ai_qa_hub`, `ai_extract_freeform`, `ai_extract_structured_from_fields`, `ai_extract_structured_from_metadata_template`, `ask_agent` | ### Collaboration context columns | Column | Populated for | | - | - | | Collaboration ID | `create_collaboration`, `update_collaboration` | | Collaboration Role | `create_collaboration`, `update_collaboration` | ### Metadata context columns | Column | Populated for | | - | - | | Metadata Template | `set_file_metadata`, `set_folder_metadata` | | Metadata Operations | `set_file_metadata`, `set_folder_metadata` | | Template Key | `create_metadata_template`, `update_metadata_template` | ## What this report does not include This report includes only actions that generate an admin event and that Box can attribute to a third-party MCP integration. Use the [MCP Tool Calls Report](/en/box-admin-tools/reporting-and-insights/mcp-tool-calls-report) to count every tool call, including calls that never appear here. The report does not include: * Identity checks, search, and listing or read-only lookup tools, such as `who_am_i`, `search_files_keyword`, `list_folder_content_by_folder_id`, `get_file_details`, and `list_hubs` * Creating a hub, copying a hub, or adding items to a hub, which cannot be tied to a specific MCP integration * Updates to a hub, which do not generate an admin event * Previews of files that are not in a renderable format Box AI queries against a hub are included. They populate the AI and file context columns.