AI agents call search_repos to retrieve information from VibeServe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query against GitHub's public repository data and returns informational results (stars, forks, topics). It retrieves and displays data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could retrieve unwanted repo information but cannot harm systems or data. Classification: Read with low severity.
From the tool's definition Tool description states 'Search trending GitHub repos by query. Returns top 20 results with stars, forks, topics.' The verb 'Search' and the output description (returns data) indicate read-only retrieval with no side effects.
Attacks that exploit this kind of access
Search trending GitHub repos by query. Returns top 20 results with stars, forks, topics. It is categorised as a Read tool in the VibeServe MCP Server, which means it retrieves data without modifying state.
Register the VibeServe MCP server in PolicyLayer and add a rule for search_repos: 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 VibeServe. Nothing to install.
search_repos 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 search_repos 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 search_repos. 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.
search_repos is provided by the VibeServe MCP server (ncsound919/vibeserve). 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 →