AI agents call compare_branches_tags to retrieve information from Mcp Gitee without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
base | string | Yes | The base branch, tag, or commit SHA to compare from |
head | string | Yes | The head branch, tag, or commit SHA to compare to |
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) |
Parameters from the server's own tool schema.
The compare_branches_tags tool performs a read-only comparison operation. It queries repository state to show differences between code versions but does not create, modify, delete, or execute any changes. This is a data retrieval operation with no side effects, fitting the Read category.
From the tool's definition Tool description states 'Compare two branches, tags, or commits in a repository' — a comparison operation that retrieves and displays differences without modifying any data.
Attacks that exploit this kind of access
Compare two branches, tags, or commits in a repository. It is categorised as a Read tool in the Mcp Gitee MCP Server, which means it retrieves data without modifying state.
compare_branches_tags accepts 4 parameters: base, head, repo, owner. Required: base, head, repo, owner. 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 compare_branches_tags: 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.
compare_branches_tags is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the compare_branches_tags 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 compare_branches_tags. 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.
compare_branches_tags 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 →