更新 Gitee 仓库中的 Pull Request
AI agents use update_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.
Updating a pull request modifies its state, title, description, or labels, but these changes are reversible and do not irreversibly delete data. The tool falls under Write category rather than Execute (which would apply if it merged or executed CI/CD) or Destructive (which would apply to closing/deletion).
From the tool's definition Tool name 'update_pull_request' and description '更新 Gitee 仓库中的 Pull Request' (Update Pull Request in Gitee repository) indicates modification of existing pull request data.
Documented attack patterns abuse exactly the kind of access update_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 update_pull_request:
{
"version": "1",
"default": "deny",
"tools": {
"update_pull_request": {
"limits": [
{
"counter": "update_pull_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_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 update_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.
update_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 update_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 update_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.
update_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.