Search npm for packages by keywords, sorted by depguard quality score. Use when you need to find packages but already know the keywords.
AI agents call depguard_search to retrieve information from Depguard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a package registry (npm) to retrieve package metadata filtered by keywords. It is fundamentally a read-only search operation with no side effects, no data modification, and no code execution. The output is informational results used to help identify packages. The 'depguard quality score' sorting adds context but does not change the nature of the operation from retrieval to any higher-risk category.
From the tool's definition Tool performs search and retrieval of package information ('Search npm for packages by keywords') with sorting by quality metrics. No creation, modification, deletion, or execution of code occurs.
Documented attack patterns abuse exactly the kind of access depguard_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Depguard, and nothing reaches the server without passing your rules. This is the rule we recommend for depguard_search:
{
"version": "1",
"default": "deny",
"tools": {
"depguard_search": {}
}
} depguard_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search npm for packages by keywords, sorted by depguard quality score. Use when you need to find packages but already know the keywords. It is categorised as a Read tool in the Depguard MCP Server, which means it retrieves data without modifying state.
Register the Depguard MCP server in PolicyLayer and add a rule for depguard_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 Depguard. Nothing to install.
depguard_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 depguard_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 depguard_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.
depguard_search is provided by the Depguard MCP server (mopanc/depguard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Depguard, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Depguard tools catalogued and risk-classified — across an index of 43,000+ MCP servers.