Requirements
- A connected MCP client with the FullHunt server loaded
- A valid API key
- Account access for any Enterprise, Nexus, or OEM tools in the workflow
Step 1: verify access
auth_status tool call. Do not use the obsolete get_my_ip verification prompt.
Step 2: search
search tool classifies common domain, host, CVE, organization, and free-text queries. It returns stubs intended for a subsequent fetch call.
Step 3: fetch one result
Step 4: make evidence-driven pivots
After reviewing the fetched result, call named tools only when the next question requires them:Required output contract
Safety and repeatability
- Specify passive tools when active scanning is not required.
- Require confirmation before
fullhunt_scan,enterprise_on_demand_scans, oroem_on_demand_scan. - Limit tool calls and pagination per run.
- Store results, identifiers, and timestamps outside the conversation.
- Require the model to identify uncertainty and absent fields.
- Re-run the same prompt against a fixed test input after tool or model changes.
