List repositories for an org or user.
AI agents call list_repositories to retrieve information from Ghe Mcp Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves repository metadata for an organization or user. It performs no creation, modification, deletion, or execution of code. While the repositories listed may include private repos (per the server description), the operation itself is non-destructive read-only access. The low severity reflects that listing repos provides discovery information but does not grant the ability to modify or delete them.
From the tool's definition Tool name 'list_repositories' and description 'List repositories for an org or user' indicate a query/retrieval operation with no data modification.
Attacks that exploit this kind of access
List repositories for an org or user. It is categorised as a Read tool in the Ghe Mcp Gateway MCP Server, which means it retrieves data without modifying state.
Register the Ghe Mcp Gateway MCP server in PolicyLayer and add a rule for list_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 Ghe Mcp Gateway. Nothing to install.
list_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 list_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 list_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.
list_repositories is provided by the Ghe Mcp Gateway MCP server (mholzinger/ghe-mcp-gateway). 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 →