get_trending
Live trending packages with rank-delta and weekly growth %. USE WHEN: 'what is rising in npm/PyPI/Cargo right now'; recommendation not biased by training-data cutoff. RETURNS: {items[]: {name, rank, rank_delta, weekly_growth_pct}}.
This record as markdown: /tools/dev-depscope-mcp/get-trending.md
What get_trending does on Depscope
AI agents call get_trending to retrieve information from Depscope 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 |
|---|---|---|---|
limit | integer | — | Max results, 1-50. Default 20. |
scope | string | — | Time window. Defaults to week. |
ecosystem | string | — | Optional. If omitted returns cross-ecosystem trending. |
Parameters from the server's own tool schema.
Why get_trending is rated Low
get_trending queries trending package data without side effects. It retrieves and displays aggregated package statistics (rank, growth metrics) for informational purposes only. There is no data creation, modification, deletion, code execution, or financial transaction.
From the tool's definition Tool retrieves 'live trending packages' and 'RETURNS' data in the form of {items[], name, rank, rank_delta, weekly_growth_pct}. No mutation, deletion, or execution described.
Attacks that exploit this kind of access
The rule that runs get_trending safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Depscope, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_trending, this is the rule to start with:
get_trending 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 Depscope, apply this rule, and every get_trending call is checked against it from then on.
Questions about get_trending
Live trending packages with rank-delta and weekly growth %. USE WHEN: 'what is rising in npm/PyPI/Cargo right now'; recommendation not biased by training-data cutoff. RETURNS: {items[]: {name, rank, rank_delta, weekly_growth_pct}}. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
get_trending accepts 3 parameters: limit, scope, ecosystem. The full parameter table on this page comes from the server's own tool schema.
Register the Depscope MCP server in PolicyLayer and add a rule for get_trending: 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 Depscope. Nothing to install.
get_trending 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 get_trending 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 get_trending. 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.
get_trending is provided by the Depscope MCP server (cuttalo/depscope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Depscope, and thousands of servers like it.
This server
Across the catalogue