Search and rank repositories with a simple Repo Radar score.
AI agents call rank_repositories to retrieve information from Repo Radar MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and ranks existing GitHub repository metadata to help users discover and compare projects. It has no side effects, does not modify any state, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an agent might rank irrelevant repositories or waste API quota, but cannot damage data or systems.
From the tool's definition Tool description states it 'Search and rank repositories' which are retrieval and ranking operations with no modification of data.
Attacks that exploit this kind of access
Search and rank repositories with a simple Repo Radar score. It is categorised as a Read tool in the Repo Radar MCP MCP Server, which means it retrieves data without modifying state.
Register the Repo Radar MCP server in PolicyLayer and add a rule for rank_repositories: 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 Repo Radar MCP. Nothing to install.
rank_repositories 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 rank_repositories 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 rank_repositories. 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.
rank_repositories is provided by the Repo Radar MCP server (javiermorron/repo-radar-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 →