create_pull_request · GitHub See MCP Server MCP

WHAT IT DOES

What create_pull_request does on GitHub See MCP Server

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

WHY IT NEEDS A POLICY

Why create_pull_request needs a policy

This tool creates a new pull request, a reversible modification to a repository's state. It does not execute arbitrary code, delete data, or move money. The high severity reflects that malicious PR creation could enable supply chain attacks, inject malicious code into review workflows, or disrupt development processes, even though the action itself is technically reversible.

From the tool's definition Tool name 'create_pull_request' and description 'Create a new pull request' indicate creation of a new artifact within a repository, which is reversible (PRs can be closed/deleted).

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 See 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. It is categorised as a Write tool in the GitHub See 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 See 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 See 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 See MCP Server MCP server (jesusmaster/github-see-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.