npm_dist_tags
List a package's dist-tags (latest, beta, ...) so you can see what installs by default.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/npm-dist-tags.md
What npm_dist_tags does on UnClick
AI agents call npm_dist_tags 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, e.g. @unclick/mcp-server. |
token | string | — | npm access token (optional; needed only for private packages). |
Parameters from the server's own tool schema.
Why npm_dist_tags is rated Low
This tool retrieves and lists existing dist-tags (metadata) from an npm package without creating, modifying, deleting, or executing anything. It is a read-only query operation with minimal security impact—even if misused, an AI agent could only gather information about package versions without affecting systems or data.
From the tool's definition Tool name is 'npm_dist_tags' and description states 'List a package's dist-tags', which is a retrieval operation with no modification or side effects. The action is to query and display metadata about npm package distribution tags.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs npm_dist_tags 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_dist_tags, this is the rule to start with:
npm_dist_tags 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_dist_tags call is checked against it from then on.
Questions about npm_dist_tags
List a package's dist-tags (latest, beta, ...) so you can see what installs by default. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
npm_dist_tags accepts 2 parameters: name, token. 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_dist_tags: 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_dist_tags 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_dist_tags 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_dist_tags. 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_dist_tags 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