当用户要求预览当前/指定分支上下文、查看会发送给 API 模型的上下文时调用。
AI agents call get_branch_context_preview 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 displays branch context information to show what would be sent to an API model. It is purely informational with no side effects, matching the 'Read' category definition of retrieving or querying data without side effects.
From the tool's definition Tool name 'get_branch_context_preview' and description indicate retrieval of branch context preview ('预览当前/指定分支上下文' = 'preview current/specified branch context'). The verb '查看' (view/see) confirms it retrieves data for display without modification.
Attacks that exploit this kind of access
当用户要求预览当前/指定分支上下文、查看会发送给 API 模型的上下文时调用。. 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_context_preview: 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_context_preview 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_context_preview 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_context_preview. 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_context_preview 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 →