Fetch trending GitHub repositories by stars today/this week/this month. Filter by programming language and topic. AI/ML repositories and agentic frameworks are highlighted. Use this tool when: - A research agent is discovering new tools, frameworks, or libraries gaining traction - An agent wants ...
AI agents call get_github_trending to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval tool that queries publicly available GitHub trending information with no side effects, state changes, code execution, or financial implications. The use cases explicitly describe discovery and intelligence gathering activities. Severity is low because misuse would merely return irrelevant or voluminous data without affecting systems or data integrity.
From the tool's definition Tool fetches and filters public GitHub trending repository data (name, owner, description, stars, language, topics). Uses verbs 'Fetch' and 'Filter' with no modification or execution capability. Returns read-only metadata about public repositories.
Attacks that exploit this kind of access
Fetch trending GitHub repositories by stars today/this week/this month. Filter by programming language and topic. AI/ML repositories and agentic frameworks are highlighted. Use this tool when: - A research agent is discovering new tools, frameworks, or libraries gaining traction - An agent wants early signals on emerging tech trends before they go mainstream - You need to find the hottest open-source projects in a specific domain - A developer agent is scouting for relevant libraries to recommend or integrate Returns per repo: name, owner, description, stars, stars_today, language, topics, url, breakthrough_signal (if exceptional growth). Example: getGithubTrending({ topic:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_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 Omni Service Node. Nothing to install.
get_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 get_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 get_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.
get_github_trending is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →