InsightAppSec MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INSIGHTAPPSEC_REGION | No | The region for your InsightAppSec account. Supported: us, eu, ap, ca, au | us |
| INSIGHTAPPSEC_API_KEY | Yes | Your Rapid7 InsightAppSec API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_appsA | List all applications with optional pagination and sorting |
| get_appB | Get detailed information about a specific application |
| create_appC | Create a new application |
| update_appA | Update an existing application |
| delete_appA | Delete an application. This will also delete all associated scan configs, scans, and vulnerabilities. |
| manage_app_tagsB | Add or remove tags from an application |
| list_scansB | List scans with optional pagination, sorting, and filtering |
| get_scanB | Get detailed information about a specific scan |
| submit_scanA | Submit a new scan based on a scan configuration |
| delete_scanA | Delete a scan. Only scans in FAILED status can be deleted. |
| control_scanB | Control a running scan (pause, resume, stop, or cancel) |
| get_scan_execution_detailsA | Get real-time execution metrics for a running or completed scan |
| get_scan_engine_eventsA | Get engine event logs for a scan |
| list_scan_configsB | List scan configurations with optional pagination |
| get_scan_configB | Get detailed information about a specific scan configuration |
| create_scan_configA | Create a new scan configuration for an application |
| update_scan_configC | Update an existing scan configuration |
| delete_scan_configB | Delete a scan configuration |
| list_vulnerabilitiesC | List vulnerabilities with optional pagination, sorting, and filtering |
| get_vulnerabilityA | Get detailed information about a specific vulnerability |
| update_vulnerabilityA | Update the status or severity of a vulnerability |
| get_vulnerability_discoveriesB | Get the discovery history for a vulnerability |
| list_vulnerability_commentsA | List all comments on a vulnerability |
| add_vulnerability_commentC | Add a comment to a vulnerability |
| list_schedulesA | List scan schedules with optional pagination |
| get_scheduleA | Get detailed information about a specific schedule |
| create_scheduleB | Create a new scan schedule for automated recurring scans |
| update_scheduleB | Update an existing scan schedule |
| delete_scheduleB | Delete a scan schedule |
| list_blackoutsB | List blackout windows with optional pagination |
| get_blackoutA | Get detailed information about a specific blackout window |
| create_blackoutA | Create a blackout window to prevent scans during maintenance periods |
| update_blackoutC | Update an existing blackout window |
| delete_blackoutB | Delete a blackout window |
| list_enginesB | List registered scan engines with optional pagination |
| get_engineA | Get detailed information about a specific scan engine |
| list_engine_groupsB | List engine groups with optional pagination |
| get_engine_groupB | Get detailed information about a specific engine group |
| list_reportsC | List generated reports with optional pagination |
| generate_reportB | Generate a new vulnerability report for an application or scan |
| get_report_statusB | Get the status and details of a generated report |
| searchA | Universal search across InsightAppSec resources using DSL query syntax. Examples:
Query operators: =, !=, <, >, <=, >=, CONTAINS, IN, AND, OR |
| list_filesA | List all files for an application (macros, traffic files, selenium scripts, etc.) |
| get_fileA | Get file metadata by ID |
| create_fileA | Create file metadata entry. After creating, use upload_file_content to upload the actual file. Supported file types:
|
| upload_file_contentA | Upload binary file content. The file metadata must be created first using create_file. |
| delete_fileB | Delete a file from an application |
| download_fileB | Download file content as base64-encoded string |
| get_scan_config_optionsB | Get the full scan configuration options including authentication settings |
| configure_form_authB | Configure form-based authentication (username/password login) for a scan configuration |
| configure_oauthB | Configure OAuth 2.0 authentication for a scan configuration |
| configure_token_replacementA | Configure global token replacement rules to extract tokens from responses and inject them into subsequent requests. Use this for dynamic tokens like CSRF tokens, API keys, or session identifiers that need to be captured and replayed. |
| configure_session_handlingC | Configure session management including cookie handling and automatic re-login on session loss |
| configure_csrf_handlingC | Configure automatic CSRF token detection and injection |
| configure_macro_authC | Configure macro-based authentication using a previously uploaded macro file |
| configure_traffic_authA | Configure traffic-based authentication using a previously uploaded traffic file (.har, .trec, .saz) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 56 tools
Most tools are clearly distinct by resource and action, such as list_apps vs create_app. However, the several scan-related getters (get_scan, get_scan_execution_details, get_scan_engine_events) could cause confusion, and the universal search tool overlaps with list functions.
The vast majority follow the verb_noun pattern with snake_case, e.g., list_schedules, create_scan_config. Minor deviations like manage_app_tags and control_scan, while still understandable, break the otherwise consistent CRUD-oriented naming.
With 56 tools, this far exceeds the recommended range of 3-15 and even the borderline 16-25. While the API scope is broad, many tools could be consolidated (e.g., all configure_* authentication tools), making the set feel oversized and harder to navigate.
The tool set provides thorough lifecycle coverage across multiple domains: applications, scans, scan configurations, vulnerabilities, schedules, blackouts, files, reports, and auth settings. CRUD operations are consistently present, and even edge cases like scan control and file uploads are included, leaving no major gaps.