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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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)
Attacks that exploit this kind of access
The rule that runs github_pr_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_pr_create, this is the rule to start with:
github_pr_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every github_pr_create call is checked against it from then on.
Questions about github_pr_create
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.
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.
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.
github_pr_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
This server
Across the catalogue