当用户要求查看某个 GitBranchMCP 分支笔记、分支结论或已保存记录时调用。
AI agents call get_branch_notes 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 stored information (branch notes, conclusions, saved records) without creating, modifying, deleting, or executing any operations. It has no side effects beyond data retrieval. The narrow scope (viewing notes in a local note-taking system) and read-only nature result in low severity—misuse would only expose information already stored in the system.
From the tool's definition Tool description states it retrieves 'branch notes, branch conclusions or saved records' when users request to view them. The verb 'view' and context of retrieving existing data without modification indicates a read-only operation.
Attacks that exploit this kind of access
当用户要求查看某个 GitBranchMCP 分支笔记、分支结论或已保存记录时调用。. 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_notes: 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_notes 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_notes 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_notes. 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_notes 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 →