MCP Tools

Available tools

The MCP server provides 22 tools that map to Intruder API endpoints. Your AI assistant picks the tools it needs based on your request, so you don't need to name them yourself.

Tools marked ✎ make changes to your Intruder account. Most AI assistants ask you to approve each tool call before it runs.

Account

ToolDescription
get_userReturns the email address of the account the API access token belongs to
get_statusChecks the Intruder API is reachable
list_licensesShows infrastructure and application license totals, available counts and consumed counts. Licenses are tied to a target for 30 days once used.

Targets

ToolDescriptionKey parameters
list_targetsLists all targets with their IDs, addresses, hostnames and status (live, license_exceeded, unscanned, unresponsive, agent_uninstalled)—
create_targets ✎Adds one or more targets to your accountaddresses: list of target addresses (e.g. ['example.com', 'test.com'])
delete_target ✎Removes a target from your accounttarget_id

Tags

ToolDescriptionKey parameters
list_tagsLists all tags in your account, optionally filtered by targettarget_address (optional)
create_target_tag ✎Adds a tag to a target (max 40 characters)target_id, name
delete_target_tag ✎Removes a tag from a targettarget_id, tag_name

Attack surface

ToolDescriptionKey parameters
list_network_servicesLists the network services (open ports) found on your targets, with product, version, web page title, TLS certificate expiry, web application firewall, and when each service was first and last seenAll optional: target_ids, tag_names, ports, protocols (tcp, udp), names (e.g. https, ssh), ssl_cert_expired, ssl_cert_expiring_within_days, ssl_cert_expiry_after, ssl_cert_expiry_before, search, offset

Scans

ToolDescriptionKey parameters
list_scansLists scans with optional filtersstatus (optional): in_progress, completed, cancelled, cancelled_no_active_targets, cancelled_no_valid_targets, analysing_results; scan_type (optional): see Scan types
get_scanRetrieves full details of a scan, including status, timestamps and target listscan_id
create_scan ✎Starts a scan on specific targets or tagged targetstarget_addresses (optional), tag_names (optional)
cancel_scan ✎Cancels a running scanscan_id

Scan schedules

ToolDescriptionKey parameters
list_scan_schedulesLists all scan schedules—
create_scan_schedule ✎Creates a recurring scan schedulename, first_scan_time (in the future and on the hour), scan_frequency (daily, weekly, monthly, quarterly), target_ids and/or tag_names, plus optional throttled, web_ports_only, upload_to_drata, upload_to_vanta
update_scan_schedule ✎Changes a scan schedule; only the fields you give are changedschedule_id, plus any of the fields above
delete_scan_schedule ✎Deletes a scan scheduleschedule_id

Issues and occurrences

ToolDescriptionKey parameters
list_issuesLists issues with optional filterstarget_addresses, tag_names, snoozed, severity (critical, high, medium, low), all optional
list_occurrencesLists all occurrences of an issueissue_id, plus optional target_addresses, tag_names, snoozed
get_scanner_outputRetrieves raw scanner output for an occurrence, including plugin details, CVEs and scan evidenceissue_id, occurrence_id
snooze_occurrence ✎Snoozes an occurrence of an issueissue_id, occurrence_id, reason (ACCEPT_RISK, FALSE_POSITIVE, MITIGATING_CONTROLS), plus optional details, duration and duration_type (day, week, month, forever)

Note: To snooze a whole issue, the assistant lists its occurrences and snoozes each one. Snoozing an entire issue in one call is no longer supported by the API.


Scan types explained

When listing or filtering scans, the scan_type parameter shows how the scan was started:

Scan typeWhat it means
assessment_scheduleScans that run on a regular schedule
new_serviceTriggered when a new service is exposed on a target
cloudbot_new_targetTriggered when Cloud sync discovers a new target in a connected cloud account
rapid_remediationUser-triggered scan to check whether a specific issue has been fixed
advisoryAn issue created by the Intruder security team based on their manual work
cloud_securityScans of cloud accounts, checking the configuration of the resources in the cloud account
container_imageScans of container images from a connected container registry, such as Docker Hub

Did this page help you?