pr-create
Creates a new pull request. Returns structured data with PR number and URL.
This record as markdown: /tools/io-github-dave-london-pare-search/pr-create.md
What pr-create does on Search
AI agents use pr-create to create or update resources in Search, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Search environment.
Why pr-create is rated Medium
Creating a pull request modifies repository state and creates new Git-related data structures. This is reversible (PRs can be closed/deleted) but has significant blast radius if triggered incorrectly—it could spam repositories, create unwanted PRs, or trigger CI/CD pipelines. This qualifies as Write rather than Execute because the tool's primary purpose is data creation, not arbitrary code execution.
From the tool's definition Tool name 'pr-create' and description 'Creates a new pull request' indicate an action that modifies repository state by creating new PR objects.
Attacks that exploit this kind of access
The rule that runs pr-create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Search, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pr-create, this is the rule to start with:
pr-create 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 Search, apply this rule, and every pr-create call is checked against it from then on.
Questions about pr-create
Creates a new pull request. Returns structured data with PR number and URL. It is categorised as a Write tool in the Search MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Search MCP server in PolicyLayer and add a rule for pr-create: 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 Search. Nothing to install.
pr-create 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 pr-create 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 pr-create. 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.
pr-create is provided by the Search MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Search, and thousands of servers like it.
This server
Across the catalogue