npm_whoami
Verify the saved npm access token and return the account it belongs to.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/npm-whoami.md
What npm_whoami does on UnClick
AI agents call npm_whoami 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 |
|---|---|---|---|
token | string | — | npm access token (optional if saved or set as NPM_TOKEN). |
Parameters from the server's own tool schema.
Why npm_whoami is rated Low
This tool performs an identity verification check (whoami pattern) that queries the npm registry to return account information associated with a token. It has no side effects—it neither modifies data, executes code, deletes resources, nor moves funds. The blast radius is minimal: an attacker could only learn which npm account is configured locally, which is low-sensitivity metadata.
From the tool's definition Tool name 'npm_whoami' and description 'Verify the saved npm access token and return the account it belongs to' indicate a read-only query operation that retrieves identity information without modifying or executing anything.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs npm_whoami 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_whoami, this is the rule to start with:
npm_whoami 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_whoami call is checked against it from then on.
Questions about npm_whoami
Verify the saved npm access token and return the account it belongs to. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
npm_whoami accepts 1 parameter: token. 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_whoami: 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_whoami 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_whoami 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_whoami. 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_whoami 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