get_pull_request

THE RISK

Low Risk

Why get_pull_request needs a policy

This tool retrieves information about a pull request. It is a query/fetch operation that does not create, modify, delete, or execute any code. It has no side effects and presents minimal risk even if called by an AI agent with arbitrary arguments.

From the tool's definition Tool name 'get_pull_request' and description '获取 Gitee 仓库中的特定 Pull Request' (Get a specific Pull Request from a Gitee repository) indicate data retrieval with no modification or execution of code.

Documented attack patterns abuse exactly the kind of access get_pull_request gives an agent:

POLICY

How to control get_pull_request

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 get_pull_request:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_pull_request": {}
  }
}

get_pull_request is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Gitee — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Gitee tools

Write add_issue_comment 向 Gitee 仓库中的 Issue 添加评论 Write create_branch 在 Gitee 仓库中创建一个新分支 Write create_issue 在 Gitee 仓库中创建 Issue Write create_or_update_file 在 Gitee 仓库中创建或更新文件 Write create_pull_request 在 Gitee 仓库中创建 Pull Request Write create_repository 创建 Gitee 仓库 Write fork_repository Fork Gitee 仓库 Write merge_pull_request 合并 Gitee 仓库中的 Pull Request

All 20 Gitee tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_pull_request

What does the get_pull_request tool do? +

获取 Gitee 仓库中的特定 Pull Request. It is categorised as a Read tool in the Gitee MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pull_request? +

Register the Gitee MCP server in PolicyLayer and add a rule for get_pull_request: 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.

What risk level is get_pull_request? +

get_pull_request is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pull_request? +

Yes. Add a rate_limit block to the get_pull_request 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.

How do I block get_pull_request completely? +

Set action: deny in the PolicyLayer policy for get_pull_request. 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.

What MCP server provides get_pull_request? +

get_pull_request 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.

Enforce policy on every Gitee tool call.

Start from Gitee, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →