create-pull-request · GitHub Enterprise MCP Server MCP

WHAT IT DOES

What create-pull-request does on GitHub Enterprise MCP Server

AI agents use create-pull-request to create or update resources in GitHub Enterprise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub Enterprise MCP Server environment.

WHY IT NEEDS A POLICY

Why create-pull-request needs a policy

Creating a pull request modifies repository state by introducing a proposed change set, but this is a standard Write operation because it is reversible (PRs can be closed without merging). It does not execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial).

From the tool's definition Tool name is 'create-pull-request' and description states 'Create a new pull request in a GitHub repository'. Pull request creation is a reversible modification operation—the PR can be closed or deleted if needed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create-pull-request Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create-pull-request": {
      "limits": [
        {
          "counter": "create-pull-request_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitHub Enterprise MCP Server, so you can run agents against it safely.

FAQ

Questions about create-pull-request

What does the create-pull-request tool do? +

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

How do I enforce a policy on create-pull-request? +

Register the GitHub Enterprise MCP Server 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 Enterprise MCP Server. Nothing to install.

What risk level is create-pull-request? +

create-pull-request 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? +

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.

How do I block create-pull-request completely? +

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.

What MCP server provides create-pull-request? +

create-pull-request is provided by the GitHub Enterprise MCP Server MCP server (lessinthought/github-enterprice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.