Trending GitHub repos with AI detection — what developers are building now. WHEN TO USE: To see which GitHub repositories are trending, with automatic detection of AI/ML-related projects. Good for tech trend analysis. RETURNS: List of trending repos with stars, forks, language, description, and A...
AI agents call veroq_research_github to retrieve information from Veroq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of GitHub trending repositories and returns informational data. It retrieves public repository metadata (stars, forks, language, description, AI classification) without creating, modifying, deleting, or executing any code or operations. The cost structure (1 credit) and lack of any side effects confirm this is a simple data retrieval operation with minimal security risk.
From the tool's definition Tool description states 'Trending GitHub repos with AI detection' and 'RETURNS: List of trending repos with stars, forks, language, description, and AI classification.' The tool retrieves and lists publicly available GitHub repository metadata for trend…
Attacks that exploit this kind of access
Trending GitHub repos with AI detection — what developers are building now. WHEN TO USE: To see which GitHub repositories are trending, with automatic detection of AI/ML-related projects. Good for tech trend analysis. RETURNS: List of trending repos with stars, forks, language, description, and AI classification. COST: 1 credit. EXAMPLE: {}. It is categorised as a Read tool in the Veroq MCP Server, which means it retrieves data without modifying state.
Register the Veroq MCP server in PolicyLayer and add a rule for veroq_research_github: 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 Veroq. Nothing to install.
veroq_research_github 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 veroq_research_github 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 veroq_research_github. 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.
veroq_research_github is provided by the Veroq MCP server (veroq-ai/veroq-mcp). 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 →