当分支讨论中出现重要结论、技术选择、方案取舍、需求变更、风险或待办时调用。
AI agents use save_note to create or update resources in GitBranchMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitBranchMCP environment.
The tool creates or appends structured data (notes) to persist discussion outcomes and decisions. This is a reversible write operation—notes can be updated or deleted later. It does not execute external code, delete irreversibly, or move financial assets.
From the tool's definition Tool name 'save_note' and description indicating it is called when important conclusions, technical choices, solutions, requirement changes, risks, or tasks appear in branch discussions. This creates or modifies note data within the branch management system.
Attacks that exploit this kind of access
当分支讨论中出现重要结论、技术选择、方案取舍、需求变更、风险或待办时调用。. It is categorised as a Write tool in the GitBranchMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitBranch MCP server in PolicyLayer and add a rule for save_note: 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.
save_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_note 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 save_note. 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.
save_note 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 →