High Risk →

update_pr_branch

Update a pull request branch by rebasing on the base branch

How to control update_pr_branch ↓

What update_pr_branch does on Forgejo

AI agents invoke update_pr_branch to trigger actions in Forgejo. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why update_pr_branch needs a policy

Rebasing rewrites git history and modifies the PR branch's commit structure. This is an active git operation (rebase) that changes commit SHAs and branch state. While technically reversible in some cases, it triggers external repository operations and rewrites branch history, making it Execute-level severity. Misuse could corrupt branch history or cause conflicts at scale.

From the tool's definition Update a pull request branch by rebasing on the base branch

Documented attack patterns abuse exactly the kind of access update_pr_branch gives an agent:

How to control update_pr_branch

PolicyLayer is an MCP gateway — it sits between your AI agents and Forgejo, and nothing reaches the server without passing your rules. This is the rule we recommend for update_pr_branch:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_pr_branch": {
      "limits": [
        {
          "counter": "update_pr_branch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

update_pr_branch stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Forgejo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about update_pr_branch

What does the update_pr_branch tool do? +

Update a pull request branch by rebasing on the base branch. It is categorised as a Execute tool in the Forgejo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on update_pr_branch? +

Register the Forgejo MCP server in PolicyLayer and add a rule for update_pr_branch: 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 Forgejo. Nothing to install.

What risk level is update_pr_branch? +

update_pr_branch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit update_pr_branch? +

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

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

update_pr_branch is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Forgejo tool call.

Start from Forgejo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

103 Forgejo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.