npm_package
Look up an npm (Node.js) package: latest version, description, license, repository, last publish date, deprecation status, and last-month download count. Pair with cve_search_by_keyword to check for known vulnerabilities. Keyless.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/npm-package.md
What npm_package does on Livedatalink
AI agents call npm_package to retrieve information from Livedatalink 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 |
|---|---|---|---|
name | string | Yes | npm package name, e.g. 'express' or '@scope/pkg'. |
Parameters from the server's own tool schema.
Why npm_package is rated Low
npm_package retrieves and returns metadata about Node.js packages from a public registry. It performs a query operation with no side effects—no code execution, no data modification, no deletion, and no financial impact. The tool is explicitly designed for information lookup only. The mention of pairing with cve_search_by_keyword for vulnerability checking reinforces its read-only nature as a lookup/reference tool.
From the tool's definition Tool description states it 'Look[s] up' package metadata including version, description, license, repository, publish date, deprecation status, and download count.
Attacks that exploit this kind of access
The rule that runs npm_package safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For npm_package, this is the rule to start with:
npm_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 Livedatalink, apply this rule, and every npm_package call is checked against it from then on.
Questions about npm_package
Look up an npm (Node.js) package: latest version, description, license, repository, last publish date, deprecation status, and last-month download count. Pair with cve_search_by_keyword to check for known vulnerabilities. Keyless. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
npm_package accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for npm_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 Livedatalink. Nothing to install.
npm_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 npm_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 npm_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.
npm_package is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue