当用户想查看主线决策、已合并分支或历史摘要时调用。
AI agents call list_main_summaries 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 only retrieves and displays existing summary information from the mainline branch history. It performs a read-only query operation with no side effects, data modification, code execution, or destructive actions. The blast radius of misuse is minimal—an agent could only access information that already exists in the repository's branch notes and summaries.
From the tool's definition Tool name is 'list_main_summaries' and description indicates it retrieves summaries when users want to view mainline decisions, merged branches, or historical summaries.
Attacks that exploit this kind of access
当用户想查看主线决策、已合并分支或历史摘要时调用。. 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 list_main_summaries: 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.
list_main_summaries 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 list_main_summaries 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 list_main_summaries. 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.
list_main_summaries 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 →