AI agents use manage_pull_review to create or update resources in Mcp Gitee — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gitee environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | The path of the repository |
force | boolean | — | Whether to force approve (only for administrators, valid when action=approve) |
owner | string | Yes | The space address to which the repository belongs (enterprise, organization or personal path) |
action | string | Yes | Action to perform: approve (submit approval) or cancel (reset review status) |
number | number | Yes | The number of the pull request, must be an integer, not a float |
reset_all | boolean | — | Whether to reset all reviewers (only for administrators, valid when action=cancel) |
Parameters from the server's own tool schema.
This tool modifies pull request review status (approve/cancel), which creates or changes data in the repository's review workflow. This is reversible (approvals can be withdrawn, cancellations can be re-approved), so it falls under Write rather than Destructive or Execute.
From the tool's definition Tool description states 'Manage a pull request review (approve or cancel)' — approval and cancellation are reversible modifications to review state on a pull request.
Attacks that exploit this kind of access
Manage a pull request review (approve or cancel). It is categorised as a Write tool in the Mcp Gitee MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
manage_pull_review accepts 6 parameters: repo, force, owner, action, number, reset_all. Required: repo, owner, action, number. 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 manage_pull_review: 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.
manage_pull_review 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 manage_pull_review 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 manage_pull_review. 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.
manage_pull_review 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 →