AI agents call list_repo_pulls 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 |
|---|---|---|---|
base | string | — | Target branch name for the pull request |
head | string | — | Source branch of the PR. Format: branch or username:branch |
page | number | — | Current page number |
repo | string | Yes | Repository namespace |
sort | string | — | Sort field, default by creation time |
owner | string | Yes | Repository owner's namespace |
since | string | — | Start update time in ISO 8601 format |
state | string | — | State of the pull request |
author | string | — | PR creator's username |
labels | string | — | Comma-separated labels, e.g.: bug,performance |
tester | string | — | Tester's username |
assignee | string | — | Reviewer's username |
Parameters from the server's own tool schema.
This tool queries and retrieves a list of pull requests from a repository. It performs no creation, modification, deletion, or execution of operations. It is a straightforward data retrieval operation similar to list/get/fetch operations, placing it in the Read category with low severity.
From the tool's definition Tool name is 'list_repo_pulls' and description states 'List repository pulls' - both indicate a retrieval operation with no modification or side effects.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
List repository pulls. It is categorised as a Read tool in the Mcp Gitee MCP Server, which means it retrieves data without modifying state.
list_repo_pulls accepts 12 parameters: base, head, page, repo, sort, owner, since, state, author, labels, tester, assignee. Required: repo, owner. 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_repo_pulls: 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_repo_pulls 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_repo_pulls 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_repo_pulls. 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_repo_pulls 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 →