github_trending
List trending GitHub repositories. Returns the repositories on GitHub's trending page (market discovery).
This record as markdown: /tools/crawlora-mcp/github-trending.md
What github_trending does on Crawlora
AI agents call github_trending to retrieve information from Crawlora 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 |
|---|---|---|---|
since | string | — | Time window |
language | string | — | Programming language filter (e.g. go, python) |
Parameters from the server's own tool schema.
Why github_trending is rated Low
This tool retrieves public trending repository metadata from GitHub, comparable to browsing a public webpage. There is no capability to modify repositories, execute code, or trigger external operations. The blast radius of misuse is minimal—an agent could only discover repositories it already has public access to. Classified as Read with low severity.
From the tool's definition Queries GitHub's trending page to 'list' repositories—a read-only operation. No data is created, modified, deleted, or executed. The description explicitly states this is for 'market discovery' with no side effects.
Attacks that exploit this kind of access
The rule that runs github_trending safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_trending, this is the rule to start with:
github_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 Crawlora, apply this rule, and every github_trending call is checked against it from then on.
Questions about github_trending
List trending GitHub repositories. Returns the repositories on GitHub's trending page (market discovery). It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
github_trending accepts 2 parameters: since, language. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for github_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 Crawlora. Nothing to install.
github_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 github_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 github_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.
github_trending is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue