azure_devops_pull_request_changes

THE RISK

Low Risk

Why azure_devops_pull_request_changes needs a policy

This tool retrieves and displays code changes/diff information from an existing pull request. It performs a read-only query operation with no side effects—no code is executed, no data is modified or deleted, and no external operations are triggered. The blast radius of misuse is minimal: an AI agent could only access PR change information that may already be visible to authorized users.

From the tool's definition Tool name 'azure_devops_pull_request_changes' and description 'Get detailed code changes for a pull request' indicate retrieval of existing data with no modification, deletion, or execution capability.

Documented attack patterns abuse exactly the kind of access azure_devops_pull_request_changes gives an agent:

POLICY

How to control azure_devops_pull_request_changes

PolicyLayer is an MCP gateway — it sits between your AI agents and Cursor Azure Devops, and nothing reaches the server without passing your rules. This is the rule we recommend for azure_devops_pull_request_changes:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "azure_devops_pull_request_changes": {}
  }
}

azure_devops_pull_request_changes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Cursor Azure Devops — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Cursor Azure Devops tools

Write azure_devops_create_pr_comment Create a comment on a pull request Read azure_devops_linked_work_items Get all linked work items with their full details Read azure_devops_projects List all Azure DevOps projects in your organization. Returns project details including ID, Read azure_devops_pull_request_by_id Get detailed information about a specific pull request. Returns complete PR data including Read azure_devops_pull_request_threads Get all comment threads in a pull request. Returns thread details including comments, stat Read azure_devops_pull_requests List all pull requests in a repository. Returns comprehensive PR information including tit Read azure_devops_repositories List all Git repositories in an Azure DevOps project. Returns repository details including Read azure_devops_test_cases List all test cases for a test suite

All 20 Cursor Azure Devops tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about azure_devops_pull_request_changes

What does the azure_devops_pull_request_changes tool do? +

Get detailed code changes for a pull request. It is categorised as a Read tool in the Cursor Azure Devops MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on azure_devops_pull_request_changes? +

Register the Cursor Azure Devops MCP server in PolicyLayer and add a rule for azure_devops_pull_request_changes: 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 Cursor Azure Devops. Nothing to install.

What risk level is azure_devops_pull_request_changes? +

azure_devops_pull_request_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit azure_devops_pull_request_changes? +

Yes. Add a rate_limit block to the azure_devops_pull_request_changes 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 azure_devops_pull_request_changes completely? +

Set action: deny in the PolicyLayer policy for azure_devops_pull_request_changes. 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 azure_devops_pull_request_changes? +

azure_devops_pull_request_changes is provided by the Cursor Azure Devops MCP server (maximtitovich/cursor-azure-devops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cursor Azure Devops tool call.

Start from Cursor Azure Devops, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →