当用户要求查看某个 GitBranchMCP 分支自 fork 后新增内容、branch diff 时调用。
AI agents call get_branch_diff to retrieve information from GitBranchMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_branch_diff retrieves and displays branch differences without modifying, deleting, or executing operations. This is fundamentally a Read operation. Severity is medium rather than low because diffs could potentially expose sensitive information in code (credentials, internal logic) if an attacker constructs a malicious query, but the tool itself performs no write, destructive, or execution actions.
From the tool's definition Tool description indicates it 'queries' or 'views' differences between branches ("查看某个分支自 fork 后新增内容、branch diff"), which is a retrieval operation. The name "get_branch_diff" also suggests retrieving diff data.
Attacks that exploit this kind of access
当用户要求查看某个 GitBranchMCP 分支自 fork 后新增内容、branch diff 时调用。. It is categorised as a Read tool in the GitBranchMCP MCP Server, which means it retrieves data without modifying state.
Register the GitBranch MCP server in PolicyLayer and add a rule for get_branch_diff: 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 GitBranchMCP. Nothing to install.
get_branch_diff 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 get_branch_diff 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 get_branch_diff. 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.
get_branch_diff is provided by the GitBranch MCP server (lianggaoyuan/gitbranchmcp). 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 →