在 Gitee 仓库中创建 Pull Request
AI agents use create_pull_request to create or update resources in Gitee — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitee environment.
Creating a pull request is a write operation that creates a new entity (PR) in the repository. It modifies the repository state by introducing a new review mechanism and change proposal, but this is reversible (PRs can be closed or deleted). It does not execute code, delete data, or move funds, so it falls under Write rather than Execute or Destructive.
From the tool's definition Tool name: 'create_pull_request'; description: '在 Gitee 仓库中创建 Pull Request' (Create a Pull Request in a Gitee repository). This tool creates a new pull request object in the repository.
Documented attack patterns abuse exactly the kind of access create_pull_request 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 create_pull_request:
{
"version": "1",
"default": "deny",
"tools": {
"create_pull_request": {
"limits": [
{
"counter": "create_pull_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_pull_request stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
在 Gitee 仓库中创建 Pull Request. It is categorised as a Write tool in the Gitee MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitee MCP server in PolicyLayer and add a rule for create_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.
create_pull_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
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.