update_pull_request_branch

A write tool on the GitHub MCP server.

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/update-pull-request-branch.md

What update_pull_request_branch does on GitHub

AI agents use update_pull_request_branch to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.

Why update_pull_request_branch is rated Medium

This tool modifies an existing pull request branch, typically by merging the base branch into the PR branch (rebasing or merging). This is a reversible write operation that changes branch state but does not irreversibly delete data. Misuse could cause unwanted merges or conflicts in PRs, hence medium severity.

From the tool's definition 'Update pull request branch' - updates/modifies an existing pull request branch

Questions about update_pull_request_branch

What does the update_pull_request_branch tool do? +

update_pull_request_branch is a write tool on the GitHub MCP server. It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_pull_request_branch? +

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

What risk level is update_pull_request_branch? +

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

Can I rate-limit update_pull_request_branch? +

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

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

update_pull_request_branch is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GitHub, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GitHub's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.