vdb_request
The read-only escape hatch for vdb-api endpoints no dedicated tool covers, with its full path allowlist, size cap and truncation behaviour.
vdb_request sends a GET to a vdb-api read endpoint and returns the body unshaped. It exists so an agent can reach a new endpoint the day it ships, without waiting for a server release. Use a dedicated tool when there is one: unshaped bodies can be megabytes.
Parameters
| Parameter | Type | Default | Notes |
|---|---|---|---|
path |
string, required | Below the version segment, starting with /, matching an allowed prefix |
|
query |
object of string to string | none | Query string parameters |
version |
v1 or v2 |
v2 |
|
maxBytes |
integer 1024 to 1048576 | 262144 | Above this the body is truncated |
{ "path": "/eol/products/nodejs" }
{ "path": "/vuln/CVE-2021-44228/sightings", "query": { "limit": "5" } }
Truncation
When the serialised body is longer than maxBytes, the result is:
{ "truncated": true, "bytes": 2606571, "cap": 262144, "preview": "{\"..." }
with _meta["vulnetix/truncated"]: true alongside the usual result metadata, so a client can tell a cut-off body from a complete one without parsing the text. The earlier docs wrote this flag as _meta.truncated; the key is vulnetix/truncated. A truncated preview of a multi-megabyte record is rarely a useful answer: narrow the path or query, or use a dedicated tool. The cache TTL for every vdb_request call is 300 seconds.
Allowed path prefixes
A path must start with one of these:
/vuln/ /exploits /kev /iocs
/sightings /attack-techniques /snort-rules /yara-rules
/nuclei /vex /triage /advisories
/workarounds /affected /cwe-guidance /scorecard
/cloud-locators /packages /search/ /summary
/sources /ecosystems /product/ /eol/
/metric-types /exploit-sources /exploit-types /fix-distributions
/fixes/ /identifiers /gcve /msrc/
/timeline /vendor-trends /exploit-trends /malware-campaigns
/malware-trends /ai-discoveries /ai-assisted-exploits /ai-in-wild-exploitations
/ai-generated-malware /vulnetix-kev /raw/ /purl/
Anything else returns an error result that lists the allowed prefixes.
vdb_request uses the same credential, quota reporting, size guards and 12-call budget as every other tool.
If you call it often for the same endpoint, that is a missing tool: open an issue.