geAllUserRepo
AI agents call geAllUserRepo to retrieve information from GitHubMcpServer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves repository data for a user without modifying or executing anything. It has a blast radius limited to information disclosure of repositories the authenticated user has access to. The naming pattern and sibling context confirm it is a Read operation. Confidence is slightly reduced due to empty description, but the name and server purpose are clear indicators.
From the tool's definition Tool name 'geAllUserRepo' (likely 'getAllUserRepo') indicates listing or retrieving all repositories for a user. The sibling tools include 'getRepoActivity', 'getUserRepo', and 'getRepoMetadata' patterns, all Read operations.
Attacks that exploit this kind of access
geAllUserRepo. It is categorised as a Read tool in the GitHubMcpServer MCP Server, which means it retrieves data without modifying state.
Register the GitHubMcpServer MCP server in PolicyLayer and add a rule for geAllUserRepo: 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 GitHubMcpServer. Nothing to install.
geAllUserRepo 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 geAllUserRepo 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 geAllUserRepo. 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.
geAllUserRepo is provided by the GitHubMcpServer MCP server (moksh555/githubmcpserver). 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 →