npm_add_dist_tag
Point a dist-tag (e.g. latest) at an already-published version of a package you own.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/npm-add-dist-tag.md
What npm_add_dist_tag does on UnClick
AI agents use npm_add_dist_tag to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tag | string | Yes | The dist-tag to set, e.g. latest or beta. |
name | string | Yes | Package name, e.g. @unclick/mcp-server. |
token | string | — | npm access token (optional if saved or set as NPM_TOKEN). |
version | string | Yes | An already-published version, e.g. 0.3.110. |
Parameters from the server's own tool schema.
Why npm_add_dist_tag is rated Medium
This is a Write operation because it creates or modifies data reversibly—reassigning dist-tags changes which version users receive by default when installing a package, but the action itself is reversible (tags can be reassigned again). It is not Destructive because no data is deleted or permanently overwritten.
From the tool's definition The tool 'npm_add_dist_tag' modifies package metadata by reassigning distribution tags (e.g., 'latest') to different versions.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs npm_add_dist_tag 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_add_dist_tag, this is the rule to start with:
npm_add_dist_tag stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_add_dist_tag call is checked against it from then on.
Questions about npm_add_dist_tag
Point a dist-tag (e.g. latest) at an already-published version of a package you own. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
npm_add_dist_tag accepts 4 parameters: tag, name, token, version. Required: tag, name, version. 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_add_dist_tag: 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_add_dist_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the npm_add_dist_tag 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_add_dist_tag. 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_add_dist_tag 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