List repositories belonging to a user
AI agents call list_user_repos to retrieve information from GitHub MCP TypeScript SDK Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries public or accessible user repository metadata. It is a read-only operation that retrieves information without side effects, matching the Read category definition of 'retrieves or queries data; no side effects (search, list, get, fetch)'.
From the tool's definition Tool name 'list_user_repos' and description 'List repositories belonging to a user' indicate retrieval of repository information with no modification or deletion of data.
Attacks that exploit this kind of access
List repositories belonging to a user. It is categorised as a Read tool in the GitHub MCP TypeScript SDK Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP TypeScript SDK Server MCP server in PolicyLayer and add a rule for list_user_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 GitHub MCP TypeScript SDK Server. Nothing to install.
list_user_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 list_user_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 list_user_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.
list_user_repos is provided by the GitHub MCP TypeScript SDK Server MCP server (om-shree-0709/github-mcp-ts-sdk). 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 →