Lookup Indicator
lookup_indicatorLook up a threat indicator in OTX: an IPv4 or IPv6 address, a domain or hostname, a URL, an MD5/SHA1/SHA256 file hash, or a CVE id such as CVE-2021-4034. Returns the threat-intel pulses referencing that indicator plus observed-context fields, so it answers questions like which campaigns exploit a given CVE or whether an IP is known-malicious. type is auto-detected when omitted.
Example tool call
This call uses example arguments supplied in the tool’s input schema.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"indicator": "192.0.2.1"
},
"name": "lookup_indicator"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Force a type instead of auto-detecting. Case-insensitive and forgiving, "ip"/"ipv4"/"ip_address" all mean IPv4, "CVE" means cve, "md5"/"sha256"/"hash" all mean file. Leave it off unless auto-detection gets it wrong. | |
| indicator | No | The value to look up: IPv4, IPv6, domain, hostname, URL, MD5/SHA1/SHA256 hash, or a CVE id such as CVE-2021-4034. Auto-detected, you do not need to pass `type`. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hint | No | What to try instead, when found is false | |
| type | Yes | Detected or specified indicator type | |
| found | Yes | False when OTX has no record of this indicator | |
| pulses | Yes | Pulses containing this indicator | |
| reason | No | Why nothing was returned, when found is false | |
| context | No | Additional context fields from OTX API response | |
| indicator | Yes | The indicator being looked up | |
| pulse_count | Yes | Number of pulses referencing this indicator |