route_user_message · GitBranch MCP: Risk & Policy

WHAT IT DOES

What route_user_message does on GitBranchMCP

AI agents use route_user_message 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 route_user_message needs a policy

The tool appears to handle user message routing within the branch conversation system, which would involve storing or organizing messages—a write operation. The empty description lowers confidence, but context from sibling tools and the server's purpose (supporting branch conversations and message logging) indicates data modification rather than pure retrieval.

From the tool's definition Tool name 'route_user_message' on a server supporting 'branch management, summary merging' and 'message nodes' suggests it writes or appends messages to branch data structures.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

route_user_message Rate-limited

route_user_message 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": {
    "route_user_message": {
      "limits": [
        {
          "counter": "route_user_message_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 route_user_message

What does the route_user_message tool do? +

route_user_message. 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 route_user_message? +

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

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

Can I rate-limit route_user_message? +

Yes. Add a rate_limit block to the route_user_message 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 route_user_message completely? +

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

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