npm_get_package
Get metadata for an npm package (latest version).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/npm-get-package.md
What npm_get_package does on UnClick
AI agents call npm_get_package to retrieve information from UnClick 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 | Package name. |
Parameters from the server's own tool schema.
Why npm_get_package is rated Low
This tool queries npm's public package registry to retrieve metadata about a package (name, version, dependencies, description, etc.). It performs no modifications, deletions, or external operations—purely information retrieval. No authentication or elevated privileges are implied. Risk is low: an agent could retrieve unwanted package information, but this causes no harm or data loss.
From the tool's definition Tool name 'npm_get_package' with description 'Get metadata for an npm package (latest version)' indicates a retrieval operation. The verb 'Get' and action of fetching package metadata are read-only operations with no side effects.
Attacks that exploit this kind of access
The rule that runs npm_get_package safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For npm_get_package, this is the rule to start with:
npm_get_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 UnClick, apply this rule, and every npm_get_package call is checked against it from then on.
Questions about npm_get_package
Get metadata for an npm package (latest version). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
npm_get_package accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for npm_get_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 UnClick. Nothing to install.
npm_get_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_get_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_get_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_get_package is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue