osv.security.batch
Scan up to 100 packages at once for known vulnerabilities. Submit package+version+ecosystem triples (e.g. full requirements.txt or package.json dependencies) and get vulnerability matches for all in a single call. Ideal for full dependency tree security audits.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/osv.security.batch.md
What osv.security.batch does on Apibase
AI agents call osv.security.batch 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 |
|---|---|---|---|
queries | array | Yes | List of package+version+ecosystem to check (max 100) |
Parameters from the server's own tool schema.
Why osv.security.batch is rated Low
Queries vulnerability database without modifying data or executing code.
From the tool's definition Scan packages for known vulnerabilities, get vulnerability matches
Attacks that exploit this kind of access
The rule that runs osv.security.batch 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.batch, this is the rule to start with:
osv.security.batch 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.batch call is checked against it from then on.
Questions about osv.security.batch
Scan up to 100 packages at once for known vulnerabilities. Submit package+version+ecosystem triples (e.g. full requirements.txt or package.json dependencies) and get vulnerability matches for all in a single call. Ideal for full dependency tree security audits. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
osv.security.batch accepts 1 parameter: queries. Required: queries. 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.batch: 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.batch 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.batch 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.batch. 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.batch 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