列出当前用户的所有仓库。用于查看和管理你的GitHub仓库。
AI agents call github_list_repos to retrieve information from MCP Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves and displays information about GitHub repositories. It has no side effects, does not modify data, does not execute code, and does not involve financial transactions. The risk is low because even if misused by an AI agent, it only exposes metadata about repositories the authenticated user already owns or has access to.
From the tool's definition Tool name 'github_list_repos' and description states '列出当前用户的所有仓库' (lists all repositories of the current user) - a query operation that retrieves repository metadata without modifying or executing anything.
Attacks that exploit this kind of access
列出当前用户的所有仓库。用于查看和管理你的GitHub仓库。. It is categorised as a Read tool in the MCP Toolkit MCP Server, which means it retrieves data without modifying state.
Register the MCP Toolkit MCP server in PolicyLayer and add a rule for github_list_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 MCP Toolkit. Nothing to install.
github_list_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 github_list_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 github_list_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.
github_list_repos is provided by the MCP Toolkit MCP server (zxfgds/mcp-toolkit). 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 →