osv_scan
Known vulnerabilities for ONE package version from OSV.dev (GitHub Advisory DB, PyPA, Go, RustSec, OSS-Fuzz, distro feeds): advisory id + CVE aliases, severity (GHSA label or computed CVSS v3 base score), CVSS vectors, CWEs, fixed versions, a heuristic minimal safe upgrade, and links. npm, PyPI, ...
This record as markdown: /tools/com-it-scorptech-x402/osv-scan.md
What osv_scan does on ScorpTech x402 API
AI agents call osv_scan to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
purl | string | — | Alternative to ecosystem+package: a package URL such as pkg:pypi/jinja2@2.4.1 |
details | boolean | — | Include full advisory fields (default true) |
package | string | — | Package name (Maven: group:artifact, Go: module path). Alias: name |
version | string | — | Installed version; omit to list every advisory for the package |
ecosystem | string | — | npm, PyPI, Go, crates.io, Maven, Packagist, RubyGems, NuGet, Pub, Hex, CRAN, Debian:12, ... (aliases like pip, cargo, composer, gem accepted) |
Parameters from the server's own tool schema.
Why osv_scan is rated Low
Even though osv_scan only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs osv_scan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For osv_scan, this is the rule to start with:
osv_scan is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every osv_scan call is checked against it from then on.
Questions about osv_scan
Known vulnerabilities for ONE package version from OSV.dev (GitHub Advisory DB, PyPA, Go, RustSec, OSS-Fuzz, distro feeds): advisory id + CVE aliases, severity (GHSA label or computed CVSS v3 base score), CVSS vectors, CWEs, fixed versions, a heuristic minimal safe upgrade, and links. npm, PyPI, Go, crates.io, Maven, Packagist, RubyGems, NuGet, Pub, Hex, distros. Use POST for a whole dependency list or lockfile. Price: $0.02 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/osv-scan. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
osv_scan accepts 5 parameters: purl, details, package, version, ecosystem. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for osv_scan: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ScorpTech x402 API. Nothing to install.
osv_scan is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the osv_scan rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for osv_scan. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
osv_scan is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue