AI agents use merge_pull 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 |
owner | string | Yes | The space address to which the repository belongs (the address path of the enterprise, organization or individual) |
title | string | — | The title of the merge commit |
number | number | Yes | The number of the pull request |
description | string | — | The description of the merge commit |
merge_method | string | — | The merge method to use |
close_related_issue | boolean | — | Whether to close the related issue after merging |
prune_source_branch | boolean | — | Whether to delete the source branch after merging |
Parameters from the server's own tool schema.
Merging a pull request is a reversible write operation that modifies repository structure and history. While merges can theoretically be reverted (via revert commits or force-push), they are typically treated as committed changes in most workflows. This is less severe than Destructive (which is irreversible) but more severe than Read.
From the tool's definition Tool name 'merge_pull' and description 'Merge a pull request' indicate this modifies repository state by combining branches.
Attacks that exploit this kind of access
Merge a pull request. 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.
merge_pull accepts 8 parameters: repo, owner, title, number, description, merge_method, close_related_issue, prune_source_branch. Required: repo, owner, 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 merge_pull: 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.
merge_pull 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 merge_pull 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 merge_pull. 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.
merge_pull 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 →