This record as markdown: /tools/io-github-aifity-omnigit-mcp/create-pull-request.md
What create_pull_request does on GitHub
AI agents use create_pull_request 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 create_pull_request is rated Medium
Creating a pull request is a reversible write operation that modifies repository state by introducing a new PR, but does not permanently delete data or execute arbitrary code. The severity is medium because misuse could introduce unwanted code changes or disrupt workflows, but the changes can be reverted or the PR closed without permanent damage.
From the tool's definition Tool name 'create_pull_request' and description 'Open new pull request' indicate creation of a new pull request object in a repository.
Attacks that exploit this kind of access
The rule that runs create_pull_request 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, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every create_pull_request call is checked against it from then on.
Questions about create_pull_request
Open new pull request. 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.
Register the GitHub 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. 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 (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.
This server
Across the catalogue