New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

github_pr_create

Create a GitHub pull request from the current branch.

SERVERYaver SOURCEyaver-cli
Medium RISK CLASS
Category Write
Parameters 61 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/github-pr-create.md

What github_pr_create does on Yaver

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

ParameterTypeRequiredDescription
base string Target branch (default: repo default branch)
body string
head string Source branch (default: current)
draft boolean
title string Yes
directory string

Parameters from the server's own tool schema.

Why github_pr_create is rated Medium

Creating a pull request on GitHub is a reversible write operation — the PR can be updated or closed without data loss. It does not destroy data (not Destructive), does not involve financial transactions (not Financial), and does not execute arbitrary code on behalf of the user (not Execute, though it interacts with an external service).

From the tool's definition Tool name contains 'create' and description states 'Create a GitHub pull request from the current branch.' This creates a new pull request object in GitHub.

Risk signalsAccepts file system path (directory) · Accepts raw HTML/template content (body)

Questions about github_pr_create

What does the github_pr_create tool do? +

Create a GitHub pull request from the current branch. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does github_pr_create accept? +

github_pr_create accepts 6 parameters: base, body, head, draft, title, directory. Required: title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on github_pr_create? +

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

What risk level is github_pr_create? +

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

Can I rate-limit github_pr_create? +

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

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

github_pr_create is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Yaver, 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 Yaver'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.