create_pull_request_with_copilot

SERVERGitHub SOURCEoci:ghcr.io/github/github-mcp-server:1.3.0

Medium RISK CLASS

Category Write

Parameters 50 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/github/create-pull-request-with-copilot.md

WHAT IT DOES

What create_pull_request_with_copilot does on GitHub

AI agents use create_pull_request_with_copilot 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.

Parameter	Type	Required	Description
`repo`	string	—	Repository name. You can guess the repository name, but confirm it with the user before proceeding.
`owner`	string	—	Repository owner. You can guess the owner, but confirm it with the user before proceeding.
`title`	string	—	Title for the pull request that will be created
`base_ref`	string	—	Git reference (e.g., branch) that the agent will start its work from. If not specified, defaults to the repository's default branch
`problem_statement`	string	—	Detailed description of the task to be performed (e.g., 'Implement a feature that does X', 'Fix bug Y', etc.)

Parameters from the server's own tool schema.

RISK

Why create_pull_request_with_copilot is rated Medium

This tool creates a pull request by delegating a coding task to GitHub Copilot. Creating a pull request is a Write operation (reversible — PRs can be closed/deleted). However, severity is high because an AI agent autonomously writes and submits code changes, which could introduce vulnerabilities, unintended logic, or sensitive data exposure.

From the tool's definition create a pull request with the implementation... The agent will create a pull request

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_pull_request_with_copilot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_pull_request_with_copilot, this is the rule to start with:

create_pull_request_with_copilot Rate-limited

create_pull_request_with_copilot 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": {
    "create_pull_request_with_copilot": {
      "limits": [
        {
          "counter": "create_pull_request_with_copilot_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every create_pull_request_with_copilot call is checked against it from then on.

FAQ

Questions about create_pull_request_with_copilot

What does the create_pull_request_with_copilot tool do? +

Delegate a task to GitHub Copilot coding agent to perform in the background. The agent will create a pull request with the implementation. You should use this tool if the user asks to create a pull request to perform a specific task, or if the user asks Copilot to do something. 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.

What parameters does create_pull_request_with_copilot accept? +

create_pull_request_with_copilot accepts 5 parameters: repo, owner, title, base_ref, problem_statement. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_pull_request_with_copilot? +

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

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

Can I rate-limit create_pull_request_with_copilot? +

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

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

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

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 86 GitHub tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →