create_pr_with_content · GitHub MCP Server MCP

WHAT IT DOES

What create_pr_with_content does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why create_pr_with_content needs a policy

Creating a pull request is a reversible write operation that modifies repository state by introducing new proposed changes. While PRs can be closed/deleted, the primary action is to create new data structures. This is less severe than destructive operations (which cannot be undone) but more impactful than simple data retrieval.

From the tool's definition Tool name 'create_pr_with_content' indicates creation of pull requests with specified content. Sibling tools like 'create_issues' and 'create_milestone' are also write operations. The description is empty, limiting precision.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_pr_with_content Rate-limited

create_pr_with_content 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_pr_with_content": {
      "limits": [
        {
          "counter": "create_pr_with_content_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about create_pr_with_content

What does the create_pr_with_content tool do? +

create_pr_with_content. It is categorised as a Write tool in the GitHub 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_pr_with_content? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for create_pr_with_content: 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. Nothing to install.

What risk level is create_pr_with_content? +

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

Can I rate-limit create_pr_with_content? +

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

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

create_pr_with_content is provided by the GitHub MCP Server MCP server (rriesco/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.