append_message_node · GitBranch MCP: Risk & Policy

WHAT IT DOES

What append_message_node does on GitBranchMCP

AI agents use append_message_node 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.

WHY IT NEEDS A POLICY

Why append_message_node needs a policy

The tool appends (adds) message nodes to branches, which creates new data structures within the note-taking system. This is a Write operation—it modifies state by adding records, but the action is reversible (nodes can presumably be deleted via delete_branch or similar). While it operates on conversation data rather than executing external code, its effect is to persistently modify the application's data store.

From the tool's definition Tool description states '手动向某个分支追加 message_node' (manually append message_node to a branch), which creates/adds a new data node to the conversation graph. This is reversible data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

append_message_node Rate-limited

append_message_node stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "append_message_node": {
      "limits": [
        {
          "counter": "append_message_node_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitBranchMCP, so you can run agents against it safely.

FAQ

Questions about append_message_node

What does the append_message_node tool do? +

手动向某个分支追加 message_node，用于验证 Git-like conversation graph。. 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.

How do I enforce a policy on append_message_node? +

Register the GitBranch MCP server in PolicyLayer and add a rule for append_message_node: 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.

What risk level is append_message_node? +

append_message_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit append_message_node? +

Yes. Add a rate_limit block to the append_message_node 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.

How do I block append_message_node completely? +

Set action: deny in the PolicyLayer policy for append_message_node. 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.

What MCP server provides append_message_node? +

append_message_node 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.