create_pull_request
A write tool on the Azure DevOps MCP server.
This record as markdown: /tools/abdelrhmansror-azuredevopsmcp/create-pull-request.md
What create_pull_request does on Azure DevOps MCP Server
AI agents use create_pull_request to create or update resources in Azure DevOps MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure DevOps MCP Server environment.
Why create_pull_request is rated Medium
Creating a pull request is a reversible write operation—it commits code for review and can be closed, abandoned, or modified afterward, but does not permanently delete data or execute arbitrary code. The severity is high because misuse could introduce unreviewed/malicious code into repository review workflows, impacting development pipelines and potentially allowing bad code to merge.
From the tool's definition Tool name is 'create_pull_request' which creates a new pull request artifact in Azure DevOps. The sibling tools confirm this server manages PR lifecycle (add_pull_request_comment, get_pull_request, link_pr_to_work_item), establishing that pull requests are…
Attacks that exploit this kind of access
The rule that runs create_pull_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Azure DevOps MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_pull_request, this is the rule to start with:
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 Azure DevOps MCP Server, apply this rule, and every create_pull_request call is checked against it from then on.
Questions about create_pull_request
create_pull_request is a write tool on the Azure DevOps MCP Server MCP server. It is categorised as a Write tool in the Azure DevOps MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Azure DevOps 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 Azure DevOps 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 Azure DevOps MCP Server MCP server (abdelrhmansror/azuredevopsmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Azure DevOps MCP Server, and thousands of servers like it.
This server
Across the catalogue