create_pull_request · Server Github MCP: Risk & Policy

WHAT IT DOES

What create_pull_request does on Server Github

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

PARAMETERS

Parameter	Type	Required	Description
`base`	string	Yes	The name of the branch you want the changes pulled into
`body`	string	—	Pull request body/description
`head`	string	Yes	The name of the branch where your changes are implemented
`repo`	string	Yes	Repository name
`draft`	boolean	—	Whether to create the pull request as a draft
`owner`	string	Yes	Repository owner (username or organization)
`title`	string	Yes	Pull request title
`maintainer_can_modify`	boolean	—	Whether maintainers can modify the pull request

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why create_pull_request needs a policy

Creating a pull request modifies the repository state by introducing a new code review mechanism, but it is reversible (can be closed/deleted) and does not directly alter production code or delete data. It falls squarely into the Write category.

From the tool's definition Tool description states 'Create a new pull request' — this is a write operation that creates new data (a pull request) in a GitHub repository.

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

Questions about create_pull_request

What does the create_pull_request tool do? +

Create a new pull request in a GitHub repository. It is categorised as a Write tool in the Server Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_pull_request accept? +

create_pull_request accepts 8 parameters: base, body, head, repo, draft, owner, title, maintainer_can_modify. Required: base, head, repo, owner, title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_pull_request? +

Register the Server Github 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 Server Github. Nothing to install.

What risk level is create_pull_request? +

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 create_pull_request? +

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.

How do I block create_pull_request completely? +

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.

What MCP server provides create_pull_request? +

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