This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/npm-search.md
What npm_search does on UnClick
AI agents call npm_search 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 |
|---|---|---|---|
size | number | — | Max results (default 10, max 50). |
query | string | Yes | Package name or keyword. |
Parameters from the server's own tool schema.
Why npm_search is rated Low
This tool retrieves information about npm packages without modifying, deleting, or executing any code. It is purely a read operation that returns package metadata or search results. The low severity reflects minimal risk: an AI agent cannot misuse this to cause harm beyond potentially generating excessive search requests or gathering package intelligence.
From the tool's definition Tool name 'npm_search' and description 'Search npm packages by name or keyword' indicate a query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs npm_search 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_search, this is the rule to start with:
npm_search 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_search call is checked against it from then on.
Questions about npm_search
Search npm packages by name or keyword. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
npm_search accepts 2 parameters: size, query. Required: query. 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_search: 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_search 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_search 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_search. 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_search 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