depsdev.insights.advisories
List security advisories (from OSV) affecting a specific package version. Cross-ecosystem: npm, PyPI, Go, Maven, Cargo, NuGet. Returns advisory IDs with links to OSV.dev for full details. Complements osv.query for version-specific lookups.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/depsdev.insights.advisories.md
What depsdev.insights.advisories does on Apibase
AI agents call depsdev.insights.advisories 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 |
|---|---|---|---|
system | string | Yes | Package ecosystem: npm, pypi, go, maven, cargo, or nuget |
package | string | Yes | Package name to check for security advisories |
version | string | Yes | Package version to check (e.g. 4.17.20) |
Parameters from the server's own tool schema.
Why depsdev.insights.advisories is rated Low
Tool retrieves and queries vulnerability data without side effects or code execution.
From the tool's definition List security advisories; returns advisory IDs with links; no modification or execution
Attacks that exploit this kind of access
The rule that runs depsdev.insights.advisories 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 depsdev.insights.advisories, this is the rule to start with:
depsdev.insights.advisories 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 depsdev.insights.advisories call is checked against it from then on.
Questions about depsdev.insights.advisories
List security advisories (from OSV) affecting a specific package version. Cross-ecosystem: npm, PyPI, Go, Maven, Cargo, NuGet. Returns advisory IDs with links to OSV.dev for full details. Complements osv.query for version-specific lookups. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
depsdev.insights.advisories accepts 3 parameters: system, package, version. Required: system, package, version. 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 depsdev.insights.advisories: 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.
depsdev.insights.advisories 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 depsdev.insights.advisories 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 depsdev.insights.advisories. 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.
depsdev.insights.advisories 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