github_create_pull_request · GitHub-Jira MCP Server MCP

WHAT IT DOES

What github_create_pull_request does on GitHub-Jira MCP Server

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

WHY IT NEEDS A POLICY

Why github_create_pull_request needs a policy

Creating a pull request is a reversible write operation—it adds proposed changes to a repository without destructively altering existing code. However, it carries high severity because an AI agent could maliciously create numerous PRs, inject unwanted code, introduce security vulnerabilities, or disrupt development workflows. It is not Destructive (reversible), Execute (doesn't directly run code), or Financial.

From the tool's definition Tool name 'github_create_pull_request' indicates creation of a pull request, a write operation that modifies repository state by introducing proposed code changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

github_create_pull_request Rate-limited

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

FAQ

Questions about github_create_pull_request

What does the github_create_pull_request tool do? +

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

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

What risk level is github_create_pull_request? +

github_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 github_create_pull_request? +

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

Set action: deny in the PolicyLayer policy for github_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 github_create_pull_request? +

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