AI agents call list_user_repos to retrieve information from Mcp Gitee without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — | Search keywords |
page | number | — | Page number |
sort | string | — | Sorting method: creation time (created), update time (updated), last push time (pushed), warehouse ownership and name (full_name). Default: full_name |
type | string | — | Filter user repositories: their creation (owner), personal (personal), their membership (member), public (public), private (private), cannot be used together wi |
per_page | number | — | Number of results per page |
direction | string | — | Sorting direction: ascending (asc), descending (desc). Default: asc |
visibility | string | — | Visibility of repository |
affiliation | string | — | Affiliation between user and repository |
Parameters from the server's own tool schema.
This tool retrieves repository data for the authenticated user without creating, modifying, deleting, or executing any operations. It has minimal blast radius as it only exposes metadata about repositories the user already has access to. No irreversible changes, code execution, or financial impact possible.
From the tool's definition Tool name 'list_user_repos' with description 'List user authorized repositories' indicates data retrieval with no modification. The verb 'list' is a classic Read operation that queries and returns repository information.
Attacks that exploit this kind of access
List user authorized repositories. It is categorised as a Read tool in the Mcp Gitee MCP Server, which means it retrieves data without modifying state.
list_user_repos accepts 8 parameters: q, page, sort, type, per_page, direction, visibility, affiliation. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Gitee 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 Mcp Gitee. 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 Mcp Gitee MCP server (@gitee/mcp-gitee). 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 →