osv.security.query
Check known vulnerabilities for a specific package version in any ecosystem (npm, PyPI, Go, Maven, Rust, NuGet, 14+ more). Returns CVE/GHSA IDs, severity scores, and affected package counts. Powered by Google OSV.dev — aggregates GitHub Security Advisories, NVD, and ecosystem-native databases.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/osv.security.query.md
What osv.security.query does on Apibase
AI agents call osv.security.query to retrieve information from Apibase 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 |
|---|---|---|---|
package | string | Yes | Package name (e.g. lodash, requests, gin-gonic/gin) |
version | string | Yes | Package version to check (e.g. 4.17.20, 2.25.0) |
ecosystem | string | Yes | Package ecosystem (npm, PyPI, Go, Maven, crates.io, NuGet, Packagist, RubyGems, etc.) |
Parameters from the server's own tool schema.
Why osv.security.query is rated Low
Queries vulnerability databases without modifying data or executing code.
From the tool's definition Check known vulnerabilities, Returns CVE/GHSA IDs, severity scores
Attacks that exploit this kind of access
The rule that runs osv.security.query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For osv.security.query, this is the rule to start with:
osv.security.query 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 Apibase, apply this rule, and every osv.security.query call is checked against it from then on.
Questions about osv.security.query
Check known vulnerabilities for a specific package version in any ecosystem (npm, PyPI, Go, Maven, Rust, NuGet, 14+ more). Returns CVE/GHSA IDs, severity scores, and affected package counts. Powered by Google OSV.dev — aggregates GitHub Security Advisories, NVD, and ecosystem-native databases. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
osv.security.query accepts 3 parameters: package, version, ecosystem. Required: package, version, ecosystem. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for osv.security.query: 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 Apibase. Nothing to install.
osv.security.query 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.security.query 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.security.query. 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.security.query is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue