列出 Gitee 仓库中的 Pull Requests
AI agents call list_pull_requests to retrieve information from Gitee without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing Pull Request data from a Gitee repository. It performs no modifications, deletions, code execution, or financial transactions. It is purely informational retrieval, fitting the 'Read' category. The low severity reflects that unauthorized listing of PRs poses minimal risk compared to other tool categories.
From the tool's definition Tool name 'list_pull_requests' and description '列出 Gitee 仓库中的 Pull Requests' (List Pull Requests in Gitee repository) indicate a retrieval/query operation with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access list_pull_requests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitee, and nothing reaches the server without passing your rules. This is the rule we recommend for list_pull_requests:
{
"version": "1",
"default": "deny",
"tools": {
"list_pull_requests": {}
}
}list_pull_requests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
列出 Gitee 仓库中的 Pull Requests. It is categorised as a Read tool in the Gitee MCP Server, which means it retrieves data without modifying state.
Register the Gitee MCP server in PolicyLayer and add a rule for list_pull_requests: 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 Gitee. Nothing to install.
list_pull_requests 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_pull_requests 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_pull_requests. 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_pull_requests is provided by the Gitee MCP server (normal-coder/gitee-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitee, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Gitee tools catalogued and risk-classified — across an index of 43,000+ MCP servers.