github_create_pull_request
Crea un Pull Request de la rama
This record as markdown: /tools/inggerman-mcps/github-create-pull-request.md
What github_create_pull_request does on MCP Framework Personal
AI agents use github_create_pull_request to create or update resources in MCP Framework Personal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Framework Personal environment.
Why github_create_pull_request is rated Medium
This tool creates a pull request on GitHub, which is a write operation that modifies repository state by introducing a new PR object. While reversible (PRs can be closed), it has high severity due to potential blast radius: an agent could create unwanted PRs affecting production workflows, trigger CI/CD pipelines, or introduce malicious code into review processes.
From the tool's definition Tool name 'github_create_pull_request' and description 'Crea un Pull Request de la rama' (Creates a Pull Request from the branch) indicate creation of a pull request, which is a reversible modification to repository state.
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 MCP Framework Personal, 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 MCP Framework Personal, apply this rule, and every github_create_pull_request call is checked against it from then on.
Questions about github_create_pull_request
Crea un Pull Request de la rama. It is categorised as a Write tool in the MCP Framework Personal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Framework Personal 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 MCP Framework Personal. 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 MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Framework Personal, and thousands of servers like it.
This server
Across the catalogue