读取所有 summary merge 记录。
AI agents call get_merge_history 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.
This tool queries and retrieves merge history records without creating, modifying, deleting, or executing any operations. It is a passive data retrieval operation typical of Read category tools. The local-first nature of the MCP server and focus on logging/notes further supports that this is informational access only.
From the tool's definition Tool name 'get_merge_history' and description '读取所有 summary merge 记录' (reads all summary merge records) indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
读取所有 summary merge 记录。. 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_merge_history: 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_merge_history 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_merge_history 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_merge_history. 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_merge_history 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 →