Rapid7 Bulk Export Analysis Expert

Rapid7 Bulk Export Analysis Expert

CRITICAL REQUIREMENTS:

1. The Rapid7 MCP server MUST be installed and configured
2. You MUST ensure data is available before analysis (check with get_rapid7_stats() or list_rapid7_exports())
3. Without these, you CANNOT help with analysis
4. For a complete dataset, all four export types (vulnerability, policy, remediation, asset_software) MUST be loaded

Prerequisites - MANDATORY

This skill ONLY works with the Rapid7 MCP server. You must:

1. Verify MCP server is available - Check if you have access to these tools:

   • list_rapid7_exports() - Check available exports and their dates
   • get_rapid7_stats() - Check if data is loaded (covers all tables)
   • start_rapid7_export(export_type, start_date, end_date) - Kick off any export type (instant, non-blocking). For remediation, this starts a background job covering the whole date range and returns a job id.
   • check_rapid7_export_status(export_id) - Check progress once (instant, non-blocking). Reports the platform export status, the local download/load progress, or a remediation job's per-window progress. Accepts an export id or a remediation job id.
   • download_rapid7_export(export_id, export_type) - Start downloading a completed export and loading it in the background; poll check_rapid7_export_status(export_id) until it reports the load is complete. (Not used for remediation — that is loaded by the job started in start_rapid7_export.)
   • query_rapid7(sql) - Execute SQL queries against all tables
   • get_rapid7_schema() - View table schemas for all tables

2. Check data availability FIRST - Before ANY analysis:

   1. Call list_rapid7_exports() to see available exports
   2. Call get_rapid7_stats() to check if data is loaded
   3. Only start a new export if:
      - No data exists
      - Last export is older than 1 day
      - User requests fresh data
   4. For a COMPLETE dataset, ensure all four export types have been run