Create or update an NVM alias.
AI agents use nvm_alias to create or update resources in NVM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NVM MCP Server environment.
This tool modifies NVM alias mappings, which are persistent configuration changes affecting how Node.js versions are resolved in the environment. While not irreversible (aliases can be changed or removed), the impact is significant because a malicious agent could create misleading aliases (e.g., aliasing 'default' to an old vulnerable Node version) that could affect all downstream development workflows and CI/CD…
From the tool's definition Tool name 'nvm_alias' and description 'Create or update an NVM alias' directly indicate the tool creates or modifies NVM configuration state. The verbs 'create' and 'update' are hallmarks of Write operations.
Attacks that exploit this kind of access
Create or update an NVM alias. It is categorised as a Write tool in the NVM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NVM MCP Server MCP server in PolicyLayer and add a rule for nvm_alias: 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 NVM MCP Server. Nothing to install.
nvm_alias 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 nvm_alias 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 nvm_alias. 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.
nvm_alias is provided by the NVM MCP Server MCP server (realjacoblinder/nvm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →