github_create_pull_request
Create a new pull request
This record as markdown: /tools/io-github-alifanov-scopegate/github-create-pull-request.md
What github_create_pull_request does on ScopeGate
AI agents use github_create_pull_request to create or update resources in ScopeGate, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScopeGate environment.
Why github_create_pull_request is rated Medium
Creating a pull request modifies repository state by adding a new PR object, which is a Write operation. It is reversible (the PR can be closed or deleted). The severity is medium because misuse could create unwanted PRs that clutter repositories or introduce security-sensitive code changes, but the action itself is not destructive or critical.
From the tool's definition Tool name states 'create a pull request' which is a reversible data modification action. It creates new content (PR) in a repository but does not execute code, delete data, or move money.
Attacks that exploit this kind of access
The rule that runs github_create_pull_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_create_pull_request, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every github_create_pull_request call is checked against it from then on.
Questions about github_create_pull_request
Create a new pull request. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ScopeGate 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 ScopeGate. Nothing to install.
github_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 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.
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.
github_create_pull_request is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue