Create a new pull request in a GitHub repository
AI agents use create_pull_request to create or update resources in GitHub MCP Server Plus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub MCP Server Plus environment.
Creating a pull request is a reversible Write operation—it creates a new artifact (the PR) in the repository that can be closed or deleted if needed. While it has significant side effects (notifies reviewers, triggers CI/CD, may affect workflow), it does not irreversibly delete data nor execute arbitrary code.
From the tool's definition Tool name is 'create_pull_request' and description states 'Create a new pull request in a GitHub repository'. This creates a new code review request object in the repository, modifying the repository's pull request state.
Documented attack patterns abuse exactly the kind of access create_pull_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub MCP Server Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for create_pull_request:
{
"version": "1",
"default": "deny",
"tools": {
"create_pull_request": {
"limits": [
{
"counter": "create_pull_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_pull_request 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.
Free to start. No card required.
Create a new pull request in a GitHub repository. It is categorised as a Write tool in the GitHub MCP Server Plus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub MCP Server Plus MCP server in PolicyLayer and add a rule for create_pull_request: 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 MCP Server Plus. Nothing to install.
create_pull_request 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 create_pull_request 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 create_pull_request. 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.
create_pull_request is provided by the GitHub MCP Server Plus MCP server (phialsbasement/mcp-github-server-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitHub MCP Server Plus, 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.
18 GitHub MCP Server Plus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.