depsdev.insights.package
Get package metadata from Google deps.dev — all versions, default version, ecosystem. Covers npm, PyPI, Go, Maven, Cargo, NuGet (50M+ package versions). Complements npm/PyPI registries with cross-ecosystem unified view.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/depsdev.insights.package.md
What depsdev.insights.package does on Apibase
AI agents call depsdev.insights.package 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 (e.g. express, requests, gin-gonic/gin, log4j-core) |
Parameters from the server's own tool schema.
Why depsdev.insights.package is rated Low
Tool retrieves package metadata without modification or execution capabilities.
From the tool's definition Get package metadata from Google deps.dev — all versions, default version, ecosystem.
Attacks that exploit this kind of access
The rule that runs depsdev.insights.package 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.package, this is the rule to start with:
depsdev.insights.package 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.package call is checked against it from then on.
Questions about depsdev.insights.package
Get package metadata from Google deps.dev — all versions, default version, ecosystem. Covers npm, PyPI, Go, Maven, Cargo, NuGet (50M+ package versions). Complements npm/PyPI registries with cross-ecosystem unified view. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
depsdev.insights.package accepts 2 parameters: system, package. Required: system, package. 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.package: 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.package 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.package 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.package. 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.package 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