getTrendingRepos

Get trending GitHub repositories tracked by NodeBench AI, sorted by growth velocity.

SERVERNodebench SOURCEnodebench-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/gettrendingrepos.md

WHAT IT DOES

What getTrendingRepos does on Nodebench

AI agents call getTrendingRepos to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why getTrendingRepos is rated Low

This tool queries and retrieves trending repository data. It performs a read-only operation that returns filtered/sorted information without side effects on any system or data store. No data is created, modified, deleted, or executed. The worst-case misuse would be information gathering, which poses minimal risk.

From the tool's definition Tool name 'getTrendingRepos' and description 'Get trending GitHub repositories tracked by NodeBench AI, sorted by growth velocity' indicate data retrieval with no modification, deletion, or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getTrendingRepos safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getTrendingRepos, this is the rule to start with:

getTrendingRepos Allowed

getTrendingRepos is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getTrendingRepos": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every getTrendingRepos call is checked against it from then on.

FAQ

Questions about getTrendingRepos

What does the getTrendingRepos tool do? +

Get trending GitHub repositories tracked by NodeBench AI, sorted by growth velocity. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getTrendingRepos? +

Register the Nodebench MCP server in PolicyLayer and add a rule for getTrendingRepos: 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 Nodebench. Nothing to install.

What risk level is getTrendingRepos? +

getTrendingRepos is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getTrendingRepos? +

Yes. Add a rate_limit block to the getTrendingRepos 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.

How do I block getTrendingRepos completely? +

Set action: deny in the PolicyLayer policy for getTrendingRepos. 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.

What MCP server provides getTrendingRepos? +

getTrendingRepos is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →