scan_dependency
Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "wha...
This record as markdown: /tools/io-github-pipeworx-io-19hz/scan-dependency.md
What scan_dependency does on 19hz
AI agents call scan_dependency to retrieve information from 19hz 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 | npm package name. Scoped packages (e.g. "@types/node") are accepted. |
version | string | — | Specific version to check (e.g., "18.3.1"). Defaults to the latest published version when omitted. |
Parameters from the server's own tool schema.
Why scan_dependency is rated Low
scan_dependency is a read-only analysis tool that aggregates publicly available package metadata (license, advisories, bundle size, dependency count, ESM support, version history) from upstream services. It retrieves and summarizes data with no side effects, state changes, or resource allocation.
From the tool's definition Tool description states it performs 'Composite checks' across multiple sources (deps.dev, bundlephobia) and 'Returns a summary block' with metadata about npm packages.
Attacks that exploit this kind of access
The rule that runs scan_dependency safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 19hz, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_dependency, this is the rule to start with:
scan_dependency 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 19hz, apply this rule, and every scan_dependency call is checked against it from then on.
Questions about scan_dependency
Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Returns a summary block (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable), per-advisory detail, links, and a list of recent alternative versions. NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly. Partial failures degrade gracefully — bundlephobia's first measurement on a new version can take 5-30s; sources_failed will list it if it times out, the rest still returns. It is categorised as a Read tool in the 19hz MCP Server, which means it retrieves data without modifying state.
scan_dependency accepts 2 parameters: package, version. Required: package. The full parameter table on this page comes from the server's own tool schema.
Register the 19hz MCP server in PolicyLayer and add a rule for scan_dependency: 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 19hz. Nothing to install.
scan_dependency 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 scan_dependency 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 scan_dependency. 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.
scan_dependency is provided by the 19hz MCP server (https://gateway.pipeworx.io/19hz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 19hz, and thousands of servers like it.
This server
Across the catalogue