Create a new pull request in a repository
AI agents use create_pull_request to create or update resources in AtomGit MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AtomGit MCP Server environment.
This tool creates a new pull request, which is a write operation that modifies repository state by introducing a proposed change. While pull requests are reversible (they can be closed or abandoned without merging), they do represent a tangible creation of collaborative artifacts.
From the tool's definition Tool name 'create_pull_request' and description 'Create a new pull request in a repository' indicate creation of a reversible modification to repository state. Pull requests are standard collaborative objects that can be closed, abandoned, or reverted.
Documented attack patterns abuse exactly the kind of access create_pull_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AtomGit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_pull_request:
{
"version": "1",
"default": "deny",
"tools": {
"create_pull_request": {
"limits": [
{
"counter": "create_pull_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
Create a new pull request in a repository. It is categorised as a Write tool in the AtomGit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AtomGit 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 AtomGit MCP Server. Nothing to install.
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 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 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.
create_pull_request is provided by the AtomGit MCP Server MCP server (kaiyuanxiaobing/atomgit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AtomGit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 AtomGit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.