getUserRepo
AI agents call getUserRepo 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 GitHub repository information for a user. Despite the empty description, the naming convention ('get' prefix) and placement among similar read-only operations (getRepoActivity, getAllUserRepo) strongly indicate data retrieval without side effects. The server's stated purpose includes 'retrieving metadata' which aligns with this classification.
From the tool's definition Tool name 'getUserRepo' indicates a retrieval operation; context shows sibling tools include 'getRepoActivity' and 'geAllUserRepo' (read operations), and the server description emphasizes 'retrieving metadata' and 'monitoring' as core functions.
Attacks that exploit this kind of access
getUserRepo. 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 getUserRepo: 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.
getUserRepo 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 getUserRepo 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 getUserRepo. 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.
getUserRepo 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 →